Re: Database block lifecycle - Mailing list pgsql-general

From pinker
Subject Re: Database block lifecycle
Date
Msg-id 53EA9550.5030503@onet.eu
Whole thread Raw
In response to Re: Database block lifecycle  (John R Pierce <pierce@hogranch.com>)
Responses Re: Database block lifecycle  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
yes, I know the count is quite high. It is the max value we've
estimated, but probably on average day it will be 100-200, and yes we
use pgpool.

Am 13.08.2014 00:09, schrieb John R Pierce:
> On 8/12/2014 2:41 PM, pinker wrote:
>> btw. 512MB if we assume up to 600 connection is a reasonable value?
>
> thats an insanely high connection count, if you actually expect those
> connections to be executing concurrent queries, unless you have
> something north of 100 CPU cores.
>
> you'd be much better to have a MUCH smaller connection count, and use
> a connection pooler such as pgbouncer, in transaction mode... let 600
> client htreads connect to the pooler, but have the pooler share maybe
> 4X your CPU core/thread count of actual connections for transactions
> in progress.
>
>
>
>
>



pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Database block lifecycle
Next
From: John R Pierce
Date:
Subject: Re: Database block lifecycle