From: Matt Clark <matt@ymogen.net>
To: 'Martin Foster' <martin@ethereal-realms.org>
To: 'Kevin Barnard' <kevin.barnard@gmail.com>
Cc: 'PostgreSQL Performance' <pgsql-performance@postgresql.org>
Subject: Re: Restricting Postgres
Date: Thu, 4 Nov 2004 16:33:33 -0000
Message-ID: <002e01c4c28c$06e83df0$8300a8c0@solent> (raw)
In-Reply-To: <418A5590.5090006@ethereal-realms.org>
> Apache::DBI overall works better to what I require, even if
> it is not a
> pool per sey. Now if pgpool supported variable rate pooling like
> Apache does with it's children, it might help to even things
> out. That
> and you'd still get the spike if you have to start the webserver and
> database server at or around the same time.
I still don't quite get it though - you shouldn't be getting more than one
child per second being launched by Apache, so that's only one PG postmaster
per second, which is really a trivial load. That is unless you have
'StartServers' set high, in which case the 'obvious' answer is to lower it.
Are you launching multiple DB connections per Apache process as well?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matt@ymogen.net, martin@ethereal-realms.org, kevin.barnard@gmail.com
Subject: Re: Restricting Postgres
In-Reply-To: <002e01c4c28c$06e83df0$8300a8c0@solent>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox