>>>>> "TF" == Todd Federman <[EMAIL PROTECTED]> writes:
TF> cluster with Apache/mod_perl servers and static content on another
TF> cluster just running Apache, but even the mod_perl_tuning doc suggests
TF> that this is suboptimal for a heavily dynamic site. (Maybe it's not?)
Having your images on a separate server will save you a lot. If you
only send the dynamic content requests to your mod_perl server, then
you have minimized the amount of resource you require.
Read further into the tuning docs about using a proxy front-end
server. This makes it mostly transparent to your users and developers
where the real content comes from. I currently prefer the mod_proxy
front end solution. This lets my non-perl apache handle images and
traditional CGI's and other static content, and lets the back-end
mod_perl server handle the dynamic page requests (every page is
dynamic on one of our servers.)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: [EMAIL PROTECTED] Rockville, MD +1-301-545-6996
GPG & MIME spoken here http://www.khera.org/~vivek/
