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 Apache::DBI performance with
MaxRequestsPerChild >= 100. I suspect it's negligable unless you're using
a database like Oracle (with lots of connection establishment overhead) over
a *slow* link.
I don't think there's any significant memory savings here, is there? Things
you think might share physical memory probably don't after a SQL statement
or two and some perl code gets run. Oracle certainly changes the RAM in
their connection and cursor handles, for instance.
- Barrie
