Re: Database block lifecycle - Mailing list pgsql-general

From John R Pierce
Subject Re: Database block lifecycle
Date
Msg-id 53EA909F.9040304@hogranch.com
Whole thread Raw
In response to Database block lifecycle  (pinker <pinker@onet.eu>)
Responses Re: Database block lifecycle  (pinker <pinker@onet.eu>)
List pgsql-general
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.





--
john r pierce                                      37N 122W
somewhere on the middle of the left coast



pgsql-general by date:

Previous
From: Vik Fearing
Date:
Subject: Re: OIDs for jsonb type
Next
From: pinker
Date:
Subject: Re: Database block lifecycle