You mean overall? The move to mod_perl is more because the site is so perl heavy, its perl that is driving the change more then anything else.
I just figure If I'm going to do it, I want to do as much of it as I can :).. Thanks -Chris >> -----Original Message----- >> From: Michael Bacarella [mailto:[EMAIL PROTECTED]] >> Sent: Sunday, January 05, 2003 11:40 AM >> To: Chris Faust >> Cc: MySql Mailing List >> Subject: Re: mod_perl and mySql >> >> >> Are you sure it would help? MySQL is damn fast at taking connections. >> >> When we converted to mod_perl I made a mental note to switch >> to persistent connections. It turns out that it still >> ran fast enough even though every hit results in an RDBMS >> connection. And at this point we're doing 5M of them per day. >> >> It has never been a bottleneck for us. >> >> -M >> >> > Due to ever increasing traffic I'm converting my site into mod_perl and >> > quite honestly I'm confused about persistent DB connection and >> DB connection >> > pooling.. I know there is tons of info out there on the goggle >> groups and on >> > perl.apache.com, I also picked up "Mod_Perl Developers >> cookbook" and I also >> > have the awesome "Mysql" and "MySql and Perl for the web". >> (BTW so far the >> > little mod_perl section in "MySql and Perl for the web" has proven more >> > useful then anything I've found in the whole Mod_Perl dev cookbook). --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
