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.
> But rather on a ratio of how many CPUs you have
> considering primarily what their "bound" by.
Note that when you get down to fine-tuning, you can use
mod_rewrite to direct different queries to different
back-ends on the same or different machines. For example
by sending all the database-related URLs to a certain
instance of mod_perl (on a particular port/IP) and others
to a different instance you can reduce the number of
database connections you need.
Les Mikesell
[EMAIL PROTECTED]
