From: | Michael Loftis <mloftis(at)wgops(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, slane(at)fmpro(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Scaling postgres |
Date: | 2002-04-14 19:37:21 |
Message-ID: | 3CB9DA71.9030706@wgops.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
KEepAlives must be enabled on client and server, Netscape 4 doesn't do
keep-alives, NS6 I don't know, mosta ll versions of MSIE do keep alive
if the server allows them.
Martijn van Oosterhout wrote:
>On Sat, Apr 13, 2002 at 08:45:56PM -0400, Neil Conway 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.
>>
>
>Hmm, the default is 15 seconds. So if you are expecting lots of short
>transactions, this could blow out your connection count to 200 or so.
>Depending on the situation I'd be tempted to drop that down since the costs
>of setting up connections is much lower on a LAN than over the internet
>(assuming he's running on a LAN).
>
>But a valid point notheless...
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Loftis | 2002-04-14 19:59:09 | Re: Redhat 7.2.93 performance (was:Re: PostgreSQL 7.2.1-2PGDG RPMs available for RedHat-skipjack 7.2.93 and RedHat 6.2/SPARC) |
Previous Message | Michael Loftis | 2002-04-14 19:35:25 | Re: Scaling postgres |