I’am already using pgbouncer as a connection pooler and default_pool_size
= 96.
i checked “show pools”, the max_wait was as high as 70 or more while INSERT
statement duration is about 3000ms in postgres log.
These numbers increase over time.
I’ll try RAID with more SSDs.
Thank you for your resp
On Mon, Sep 4, 2017 at 1:14 AM, 우성민 wrote:
> Hi team,
>
> I'm trying to configure postgres and pgbouncer to handle many inserts from
> many connections.
>
> Here's some details about what i want to achieve :
>
> We have more than 3000 client connections, and my server program forks
> backend pr
Jumping on Scott's observation, assuming you really do have a lot of active
connections (idle ones usually are not a problem) a general rule of thumb for
not overloading your system is keep your active connections less than (2-3) *
(number so cpus).
Sent from my iPad
> On Sep 4, 2017, at 2:15
On Mon, Sep 4, 2017 at 2:14 AM, 우성민 wrote:
> Hi team,
>
> I'm trying to configure postgres and pgbouncer to handle many inserts from
> many connections.
>
> Here's some details about what i want to achieve :
>
> We have more than 3000 client connections, and my server program forks
> backend pro
Without more information, this is my initial guess at your insert slowness problem:The symptom of this insert slowness/delayed action is delayed, granted, extend locks (locktype=extend) due to many concurrent connections trying to insert into the same table. Each insert request results in an exten
Hi team,
I'm trying to configure postgres and pgbouncer to handle many inserts from
many connections.
Here's some details about what i want to achieve :
We have more than 3000 client connections, and my server program forks
backend process for each client connections.
If backend processes se
