Re: [HACKERS] PATCH: pgbench - option to build using ppoll() forlarger connection counts - Mailing list pgsql-hackers

From Rady, Doug
Subject Re: [HACKERS] PATCH: pgbench - option to build using ppoll() forlarger connection counts
Date
Msg-id AD31EB18-832F-4300-A465-389BEBC6C16C@amazon.com
Whole thread Raw
In response to Re: [HACKERS] PATCH: pgbench - option to build using ppoll() forlarger connection counts  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Without this patch, one is limited to '(FD_SETSIZE - 10)’ number of connections.
Example of something that fails without this patch but works with the patch:

Without the patch:

$ pgbench -j 3000 -c 1500
invalid number of clients: "1500"


With the patch:

$ pgbench -j 3000 -c 1500
starting vacuum...end.
transaction type: <builtin: TPC-B (sort of)>
scaling factor: 2000
query mode: simple
number of clients: 1500
number of threads: 1500
number of transactions per client: 10
number of transactions actually processed: 15000/15000
latency average = 631.730 ms
tps = 2374.430587 (including connections establishing)
tps = 4206.524986 (excluding connections establishing)


--
doug

On 10/26/17, 04:46, "Robert Haas" <robertmhaas@gmail.com> wrote:
   On Mon, Sep 25, 2017 at 8:01 PM, Rady, Doug <radydoug@amazon.com> wrote:   > This patch enables building pgbench to
useppoll() instead of select()   >   > to allow for more than (FD_SETSIZE - 10) connections.  As implemented,   >   >
whenusing ppoll(), the only connection limitation is system resources.      So what's an example of something that
failswithout this patch but   works with the patch?      --    Robert Haas   EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company   
 


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] Timeline ID in backup_label file
Next
From: Lætitia Avrot
Date:
Subject: [HACKERS] Adding table_constraint description in ALTER TABLE synopsis