On Wed, 26 Apr 2000, Leslie Mikesell wrote:
> According to [EMAIL PROTECTED]:
> >
> > So, overall..., I think that you should consider how many modperl
> > processes you want completely seperately from how many modproxy
> > processes you want.
>
> Apache takes care of these details for you. All you need to
> do is configure MaxClients around the absolute top number of
> mod_perls you can handle before you start pushing memory
> to swap, some small MinSpareServers and a bigger MaxSpareServers
> and the rest takes care of itself. On the front-end side
> you really don't want any process limits. If you can't
> run enough, buy more memory or turn keepalives down. Apache
> will keep the right number running for the work you are
> doing - and the TCP listen queue will hold a few more
> connections if you are slightly short of backends.
Is there any benefit of mod_proxy over a real proxy front end like "Oops"?
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org
