Обсуждение: Re: High load average in 64-core server , no I/O wait and CPU is idle

Claudio Freire  wrote:
> Stephen Frost  wrote:
>> Rajesh Kumar. Mallah (mallah@tradeindia.com) wrote:

>>> we are actually also running out db max connections (also)
>>> ( which is currently at 600) , when that happens something at
>>> the beginning of the application stack also gets dysfunctional
>>> and it changes the very input to the system. ( think of negative
>>> feedback systems )
>>
>> Oh. Yeah, have you considered pgbouncer?
>
> Or pooling at the application level. Many ORMs support connection
> pooling and limiting out-of-the-box.
>
> In essence, postgres should never bounce connections, it should all
> be handled by the application or a previous pgbouncer, both of
> which would do it more efficient and effectively.

Stephen and Claudio have, I think, pointed you in the right
direction.  For more detail on why, see this Wiki page:

http://wiki.postgresql.org/wiki/Number_Of_Database_Connections

-Kevin