So there are two paths to go from here, the simplest don't allow more than one perl per process in the prefork mpm and cleanup any redundant code that is currently run for nothing (most of the code within #ifdef USE_ITHREADS .. #endif). Probably should introduce a new define APACHE_THREADED_MPM instead of using USE_ITHREADS.
using USE_ITHREADS never sense to me, but I figured there was more going on wrt perl than just the threaded mpm. if we can focus only on using thread logic for threaded mpm's only I think that is a much better way to proceed.
+1
for the APACHE_THREADED_MPM logic, recall this bit of wisdom from wrowe (at the end):
http://marc.theaimsgroup.com/?l=apache-test-dev&m=105785644220027&w=2
(which you probably knew before I did :)
I knew, but I'm not really agreeing with this point of having the module running under prefork and worker. What's the point? We talk about performance all the time, and having the same module run under both without recompilation comes with a price of the overhead to do run-time checks and it even requires more memory usage because for USE_ITHREADS we setup members which aren't used under prefork mpm. 99.9% of users will compile their online service to run under prefork or worker, not both. Sure it'll be more pain for developers as they will have to keep two versions around so they can experiment, but this is such a little price to pay for having an optimal performance.
So I'd rather s/USE_ITHREADS/THREADED_MPM/ and keep the prefork clean of threaded stuff.
The second is to go and fix all the places where scfg->threaded_mpm check is done to accomodate the prefork mpm as well.
if we don't keep prefork=1 interpreter then we are essentially removing any possibility for people to run under the old (stable :) Apache 1.3 model. I personally think this is a very bad idea.
What do you mean? If they don't do PerlOptions +Parent|Clone it works exactly as in 1.0. We do have some unnecessary overhead of doing things that are totally irrelevant to the prefork mpm, but it doesn't affect functionality.
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
