On Mon, 2003-10-06 at 13:36, Stas Bekman wrote:
But be careful with it. If you use the threaded mpm, it's all cool. If you use prefork it'll create 2 perl interpreters and more inside each httpd process gobbling up a lot of RAM, something that you don't want to do in production. It's OK for dev though.
I wonder if we need something similar to Apache::PerlVINC for mp2 in prefork mode.
We will need most (all?) of the mp1 tools working for mp2/prefork mpm. Notice that Apache::PerlVINC was written to solve the problem for developers using the same server to develop the same modules. It's not fast for production use. So prefork/PerlOptions +Parent is probably a better solution for developers, even though it consumes more memory.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
