I'm a little confused - why would you use two apache processes for this? It sounds like one would do just fine ...
-----Original Message----- From: David Hofmann [mailto:[EMAIL PROTECTED] Sent: Thursday, April 01, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: Connections Currently I'm in the process of converting from Perl to Mod Perl. My server is Redhat Running Apache 1.3.27, Mod Perl 1.26, and Postgre SQL 7.2.4. I have about 31-35 active process running during the busy hours. Our system use Perl to generate dynamic pages via the postgre database. 90% of our pages are generated this way. We have 1 user ID that all public web request use to access the database. On the back end I have several admin Perl scripts that we use to update the database and make changes to item descriptions. There currently 4 people that use it, and there soon to be 2 more. They each spend 3-6 hours a day actually entering and changing data. Currently most of the public side has been converted to Mod Perl. I'm debating on weather converting the Admin side is going to be good or bad for the server cause it means persistent 2 connections and I'm not sure how much load that will put on the server since the majority of the time the server not using the admin connection. Hope this kind of makes sense. Mainly I'm looking for advice on the situation. David _________________________________________________________________ Free up your inbox with MSN Hotmail Extra Storage. Multiple plans available. http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362 ave/direct/01/ -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
