On 12/19/05, Perrin Harkins <[EMAIL PROTECTED]> wrote: > > Is there a way to configure mod_perl to act more like mod_php in that > > each request gets a "fresh" interpreter to work in? > > 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. (!) Also don't most shared hosts use mod_php, not PHP/CGI? What would be the point of PHP via CGI? mod_php works just fine. (As long as you stay away from threads.) > It really isn't worth putting much effort into supporting virtual host > ISPs now that you can have your own virtual server with root for > practically nothing. A virtual server for each application is even more wasteful of memory than running a FastCGI process for each app. This is not just about shared hosting ISPs. See: "Tales of Perl optimization" http://www.perl.com/pub/a/2005/12/21/a_timely_start.html The notion of a "snapshot"-able Perl interpreter has value even outside of the web application realm. -- David
