On Thu, 2005-12-22 at 23:44 -0500, [EMAIL PROTECTED] wrote: > > Just set MaxRquestsPerChild to 1. However, most shared hosts actually > > run PHP as CGI. > > Erm.. Spawning a whole new Apache process for each request seems even > worse for performance than just launching Perl via CGI. (!)
It's not. The processes are pre-forked. Try it. > Also don't most shared hosts use mod_php, not PHP/CGI? Jonathan already answered this one. > A virtual server for each application is even more wasteful of memory > than running a FastCGI process for each app. Of course it's heavier than running a FastCGI process. It's heavier than running a separate mod_perl for each one too. What it's good for is people who can't afford dedicated hardware, but still want to actually have apache under their control, install whatever they need from CPAN, compile mod_perl themselves so it's done right, etc. > The notion of a "snapshot"-able Perl interpreter has value even > outside of the web application realm. Okay, but this is the mod_perl list and it is all about the web application realm. - Perrin
