Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 78085 invoked from network); 1 Dec 2004 23:11:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Dec 2004 23:11:15 -0000 Received: (qmail 62999 invoked by uid 500); 1 Dec 2004 23:11:04 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 62985 invoked by uid 500); 1 Dec 2004 23:11:03 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 62972 invoked by uid 99); 1 Dec 2004 23:11:03 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) From: Malcolm J Harwood To: modperl@perl.apache.org Subject: Re: DBI persistence problem Date: Wed, 1 Dec 2004 18:10:57 -0500 User-Agent: KMail/1.6.1 References: <1101949230.8848.50.camel@rfogle> <1101940759.14229.32.camel@localhost.localdomain> <1101950777.8846.61.camel@rfogle> In-Reply-To: <1101950777.8846.61.camel@rfogle> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412011810.57580.mjhlist-modperl@liminalflux.net> X-Virus-Scanned: by amavisd-new at liminalflux.net X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wednesday 1 December 2004 08:26 pm, Richard N. Fogle wrote: > 1. We disabled Apache::DBI - the server can generate thousands of > queries per second and this feature literally made the CPU catch fire. Odd. Normally (in my limited experience) it has the reverse effect as you aren't creating and destroying a connection every time. > 3. We have a disconnect at the end of each perl CGI. Not sure if it is > being reached, see no plausible reason why it shouldn't - the code isn't > that complex. Worth checking anyway. > 4. This is what we have in httpd.conf: > SetHandler perl-script > PerlHandler Apache::Registry Registry will keep any globals around, so if $dbh is global it wont destroy it (though if disconnect is being called, it should disconnect it). > 5. We easily reach 1024 webserver processes, apache 1.3. If each one is connecting to the db server (assuming you don't have any interprocess connection pooling), then that's your 1024+ db connections right there. If the connections are made but not disconnected until the end of the script, you would (I think) see a lot of "idle" connections that don't have an active query (it's already completed) because they haven't reached the end of the script and been disconnected yet. -- I always wanted to be somebody, but I should have been more specific. - Lily Tomlin -- 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