perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Vanasco <jvana...@mastersofbranding.com>
Subject Re: Question about using Apache::DBI with Postgres/MySQL
Date Thu, 18 Aug 2005 17:58:35 GMT

On Aug 18, 2005, at 1:42 PM, Perrin Harkins wrote:

>  If you can figure out a way to do
> that, you could theoretically have a separate process managing a pool 
> of
> them.  I doubt it would be worth it though.

That's pretty much what I was thinking, but I didn't really want to do 
this in a situation where one has 200 apaches and 100 mysqls - it was 
more along the lines of 100 mysql and 100 apache, and just having code 
there that makes me consciously adjust things in mod_perl so  i 
remember to adjust them in httpd.conf or sql.conf.

i might just write something for the startup file that polls 
configuration files or the sql db to make sure that it has enough 
connections for the intended amount of max_clients - and print a little 
"Hey, fix this!" warning

> With MySQL, connection times are low enough that you can get rid of
> persistent connections if scalability becomes a big issue.  Typically
> though, once you have a front-end proxy your remaining mod_perl
> processes really do all need their own database connection, so this
> might just result in some of them sitting around waiting for a
> connection.  Better to increase the allowed connections to your 
> database
> server or reduce the allowed connections to your mod_perl server.

Right now thats how everything is working. I was just thinking of ways 
to make me more aware of how many connections i need to have w/the db.

I'm also looking into going from 1 box w/apache/sql to 3 boxes 
(2apache+1sql ) as i'm moving from running 1 project on this system to 
3 projects and need more mem for apache and sql

i'm thinking about moving to pgsql for stored procedures too (yes my5 
has it, but its beta), but thats an entirely OT discussion.


Mime
View raw message