Re: Scaling postgres

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
Cc: slane(at)fmpro(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Scaling postgres
Date: 2002-04-14 01:04:38
Message-ID: 20020414110438.B32396@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Ignorance continues to thrive when intelligent people choose to do
> nothing. Speaking out against censorship and ignorance is the imperative
> of all intelligent people.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Menendez 2002-04-14 01:27:43 Query planner quirk?
Previous Message Neil Conway 2002-04-14 00:45:56 Re: Scaling postgres