On Tue, 24 Oct 2000, Jeff Horn wrote:
> However, I am also aware of a _major_ ISP that implements their email
> system using a _major_ RDBMS that has had problems that are best
> solved via connection pooling. Essentially, the time it takes them to
> search through all the cached connections is nearly as long as the
> time it is taking to read/write to the database. Although, I'm not
> implementing email as this ISP is, I think that scalability in my case
> may definitely run into similar roadblocks.
>
> I am interested in hearing from anyone that has tried to implement
> true connection pooling either within Apache or as an external
> process. I'm particularly interested in hearing about implementations
> that could be made to work or are done using Perl and DBI/DBD. I am
> mostly interested in things that are Open Source or licensed like Perl
> itself.
Having just returned from ApacheCon, I can honestly recommend looking at
mod_backhand to simply have a few servers that run the DBI pool, and have
database intensive requests go to those servers. It is a *very* cool
solution to just these sorts of scalability problems.
PS: I'll have an ApacheCon report "coming soon".
--
<Matt/>
/|| ** Director and CTO **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** Personal Web Site: http://sergeant.org/ **
\\//
//\\
// \\
