From: | Steve Lane <slane(at)fmpro(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Scaling postgres |
Date: | 2002-04-14 03:22:25 |
Message-ID: | B8DE6021.BCD4%slane@fmpro.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/13/02 7:45 PM, "Neil Conway" <nconway(at)klamath(dot)dyndns(dot)org> wrote:
> On Sun, 14 Apr 2002 10:38:06 +1000
> "Martijn van Oosterhout" <kleptog(at)svana(dot)org> wrote:
>> Also, an idling client generally does not keep a connection open to the
>> Apache server. So if you have 800 people changing webpage once a minute,
>> you're really only going to be handling 15 processes at the same time.
>
> This assumes you're not using KeepAlives, in which case an httpd child
> will wait around for KeepAliveTimeout seconds before serving other
> clients.
Ah ... Good point. I should check this. My problem with persistent
connections might be related to exactly this.
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Lane | 2002-04-14 03:24:07 | Re: Scaling postgres |
Previous Message | Steve Lane | 2002-04-14 03:21:13 | Re: Scaling postgres |