Hi again to the list,
I went back through the documentation on Apache::Session,
Apache::Session::DBIStore, and Apache::DBI, and I haven't found a
problem in the way we have implemented this. Does anyone else have
suggestions, or has anyone else experienced a similar performance hit?
Thanks,
Chris
>Date: Tue, 22 Aug 2000 10:08:11 -0400
>To: Perrin Harkins <[EMAIL PROTECTED]>
>From: Chris Brooks <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: Apache::Session and performance question
>Message-ID: <[EMAIL PROTECTED]>
>Hi, thanks for the reply,
>Yes, we are calling the module from http.conf like this:
>PerlModule Apache::DBI
>PerlRequire /www/perl/scripts/perl-startup.pl
>PerlHeaderParserHandler Carescout::SessionHandler
>The referenced startup script contains the line:
>Apache::DBI->connect_on_init( 'DBI:mysql:cs', 'nobody',
>'xxxxxxxx' );
>I added
>$Apache::DBI::DEBUG = 1;
>to the startup file, and it doesn't seem to be creating a
>new connection for every request.
>Thanks,
>Chris
>>Perrin Harkins wrote:
> > On Mon, 21 Aug 2000, Chris Brooks wrote:
> > We have a fairly simple handler responsible for maintaining
> > state on our web server. Unfortunately, when we activate
> > it, server performance drops to about 1/10th of what it is
> > without. After going through the handler and commenting
> > out parts and benchmarking (rinse, repeat), Apache::Session
> > appears to be the culprit.
> >
> > I can't believe that the use of this module should have so
> > great an effect. We have to be doing something
> > incorrectly. Any advice would be greatly appreciated.
>
> You are using Apache::DBI, right?
>
> Going to the database on every single request is going to be
> expensive. If the rest of your application doesn't normally hit the
> database it makes sense for this to have a significant impact.
>
> - Perrin
--
Chris Brooks
Director of Technology
CareScout.com
phone: (781) 431-7033 x 342
