From: Martin Foster <martin@ethereal-realms.org>
To: Matt Clark <matt@ymogen.net>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Restricting Postgres
Date: Thu, 04 Nov 2004 13:04:00 -0500
Message-ID: <418A6F10.2030309@ethereal-realms.org> (raw)
In-Reply-To: <002e01c4c28c$06e83df0$8300a8c0@solent>
References: <002e01c4c28c$06e83df0$8300a8c0@solent>
Matt Clark wrote:
>>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?
>
I have start servers set to a fairly high limit. However this would
make little different overall if I restarted the webservers to load in
new modules during a high load time. When I am averaging 145
concurrent connections before a restart, I can expect that many request
to hit the server once Apache begins to respond.
As a result, it will literally cause a spike on both machines as new
connections are initiated at a high rate. In my case I don't always
have the luxury of waiting till 0300 just to test a change.
Again, not necessarily looking for a PostgreSQL solution. I am looking
for a method that would allow the database or the OS itself to protect
the system it's hosted on. If both the database and the apache server
were on the same machine this type of scenario would be unstable to say
the least.
Martin Foster
Creator/Designer Ethereal Realms
martin@ethereal-realms.org
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: martin@ethereal-realms.org, matt@ymogen.net
Subject: Re: Restricting Postgres
In-Reply-To: <418A6F10.2030309@ethereal-realms.org>
* 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