From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Reality check |
Date: | 2010-05-28 08:09:26 |
Message-ID: | AANLkTim1QgK2n0zCbHL6KyGThlcbMluesysoPFBRHsMj@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 28 May 2010 08:56, A. Kretschmer <andreas(dot)kretschmer(at)schollglas(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2010-05-28 10:12:36 | Re: Setting up postgresql-8.3 on Debian |
Previous Message | John Gage | 2010-05-28 08:08:47 | Re: Reality check |