On 28 May 2010 08:56, A. Kretschmer <andreas.kretschmer@schollglas.com> wrote:
> In response to John Gage :
>> In other words, there are 4,500 unique users accessing the website,
>> each uniquely identified via http authentication, but only ONE
>> postgres user who they all share to access the database, which implies
>> that a single, unique postgres user will be opening and closing
>> connections to the database perhaps a thousand times a minute.
>>
>> Does this work?
>>
>> If it doesn't, are there any suggestions?
>
> I think you should consider a connection pooler like pgbouncer.
>
+1
Connections have their own overhead and I've found pgbouncer to be
effective. You may also wish to consider caching if it's not critical
they see real-time data, which will reduce the number of queries
hitting the database.
Regards
Thom
