Re: [PERFORM] recommendations for web/db connection pooling or DBD::Gofer reviews

2008-04-11 Thread Vivek Khera
On Apr 10, 2008, at 5:28 PM, Mark Stosberg wrote: So, the front-end proxy would have a number of max connections, say 200, and it would connect to another httpd/mod_perl server behind with a lower number of connections, say 20. If the backend httpd server was busy, the proxy connection to

Re: [PERFORM] recommendations for web/db connection pooling or DBD::Gofer reviews

2008-04-10 Thread Mark Stosberg
Under heavy load, Apache has the usual failure mode of spawning so many threads/processes and database connections that it just exhausts all the memory on the webserver and also kills the database. As usual, I would use lighttpd as a frontend (also serving static files) to handle the l

Re: [PERFORM] recommendations for web/db connection pooling or DBD::Gofer reviews

2008-04-08 Thread PFC
When traffic to our PostgreSQL-backed website spikes, the first resource we see being exhausted is the DB slots on the master server (currently set to about 400). I expect that as new Apache/mod_perl children are being put to us, they are creating new database connections. I'm interested in re

Re: [PERFORM] recommendations for web/db connection pooling or DBD::Gofer reviews

2008-04-07 Thread Joshua D. Drake
On Mon, 07 Apr 2008 14:36:00 -0400 Mark Stosberg <[EMAIL PROTECTED]> wrote: > I'm particularly interested in review of DBD::Gofer, which seems like > it would help with this in our Perl application: > http://search.cpan.org/dist/DBI/lib/DBD/Gofer.pm > > I realize it has limitations, like "no tr

[PERFORM] recommendations for web/db connection pooling or DBD::Gofer reviews

2008-04-07 Thread Mark Stosberg
When traffic to our PostgreSQL-backed website spikes, the first resource we see being exhausted is the DB slots on the master server (currently set to about 400). I expect that as new Apache/mod_perl children are being put to us, they are creating new database connections. I'm interested in rec