Michael Peppler wrote:
Based on preliminary tests I was able to use a 1 in 10 ratio of
database handles per httpd child processes, which, on a large site
would cut down on the number of connections that the database server
needs to handle.
I'd be interested to see how this compares with
On Wed, 6 Sep 2000, Jay Strauss wrote:
Being a database guy but new to Mod_Perl (disclaimer: If these aspects have
already been implemented and/or talked about please excuse me).
Before going down this road again, I suggest reading the definitive work
on the subject, which is a post from
Michael Peppler wrote:
The back-end is Sybase. The actual connect time isn't the issue here
(for me.) It's the sheer number of connections, and the potential
issue with the number of sockets in CLOSE_WAIT or TIME_WAIT state on
the database server. We're looking at a farm of 40 front-end
t: Wednesday, September 06, 2000 12:24 PM
Subject: Re: Poor man's connection pooling
Barrie Slaymaker writes:
Michael Peppler wrote:
Based on preliminary tests I was able to use a 1 in 10 ratio of
database handles per httpd child processes, which, on a large sit
On Wed, 6 Sep 2000, Perrin Harkins wrote:
On Wed, 6 Sep 2000, Stas Bekman wrote:
Just a small correction:
You can cause pages to become unshared in perl just by writing a variable,
^^^
so it's almost certain to happen sooner
Perrin Harkins writes:
On Tue, 5 Sep 2000, Michael Peppler wrote:
I've come across a technique that allows modperl processes to share a
pool of database handles. It's not something that I have seen
documented, so I figured I'd throw it out here.
The idea is to create a pool of
On Wed, 6 Sep 2000, Stas Bekman wrote:
Just a small correction:
You can cause pages to become unshared in perl just by writing a variable,
^^^
so it's almost certain to happen sooner or later.
Or for example calling pos() which
On Tue, Sep 05, 2000 at 10:38:48AM -0700, Michael Peppler wrote:
The idea is to create a pool of connections during the main
apache/modperl startup. [...]
This technique works with Sybase connections using either
DBI/DBD::Sybase or Sybase::CTlib (I've not tested Sybase::DBlib, nor
any
On Tue, 5 Sep 2000, Perrin Harkins wrote:
On Tue, 5 Sep 2000, Michael Peppler wrote:
I've come across a technique that allows modperl processes to share a
pool of database handles. It's not something that I have seen
documented, so I figured I'd throw it out here.
The idea is to
"MP" == Michael Peppler [EMAIL PROTECTED] writes:
MP I'd be very interested in any comments, in particular if there are any
MP downsides that I haven't considered (which is quite possible).
Sounds quite cool. Would you consider making an Apache:: module for
it?
One question that pops to
On Tue, 5 Sep 2000, Michael Peppler wrote:
Stas Bekman writes:
On Tue, 5 Sep 2000, Michael Peppler wrote:
The idea is to create a pool of connections during the main
apache/modperl startup. Because these connections end up in the code
segment for the child processes they are
I've come across a technique that allows modperl processes to share a
pool of database handles. It's not something that I have seen
documented, so I figured I'd throw it out here.
The idea is to create a pool of connections during the main
apache/modperl startup. Because these connections end
On Tue, 5 Sep 2000, Michael Peppler wrote:
I've come across a technique that allows modperl processes to share a
pool of database handles. It's not something that I have seen
documented, so I figured I'd throw it out here.
The idea is to create a pool of connections during the main
Stas Bekman writes:
On Tue, 5 Sep 2000, Michael Peppler wrote:
The idea is to create a pool of connections during the main
apache/modperl startup. Because these connections end up in the code
segment for the child processes they are completely shareable. You
populate a hash in a
14 matches
Mail list logo
