According to Michael Peppler:
> 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 servers,
> each runnning ~150 modperl procs. If each of the modperl procs opens
> one connection that's 6000 connections on the database side.
>
> Sybase can handle this, but I'd rather use a lower number, hence the
> pooling.
Are you using the lightweight httpd proxy front end setup and still
have 150 modperl httpd's per server? If not, I'd try that
approach first. I usually see about a 10:1 ratio of front
to back end servers which really cuts down on the database
connections (and the static images are served by a different set of
machines so most of this effect comes from the proxy releasing
the back end process quickly). Also, if you have pages that
do not need the database connection you could set up
mod_proxy or mod_rewrite to send those requests to a different
set of back-end servers.
Les Mikesell
[EMAIL PROTECTED]
