Elizabeth Mattijsen wrote:
At 10:03 -0500 11/24/03, Geoffrey Young wrote:
this all assumes that what is important is whether the mpm is threaded or not, not whether the threads are fixed in number or can grow, etc (which seems reasonable to me).
What _I_ am interested in, is a flag with which I could see whether it would make sense to load as much as possible, rather than on demand.
yes, that's what I gathered.
the thing is, my understanding/reading of mod_perl core leads me to believe that whenever _perl_ is threaded mod_perl uses the interpreter pool approach. from mod_perl.c:
#ifdef USE_ITHREADS static void modperl_init_clones(server_rec *s, apr_pool_t *p)
how it handles that pool underneath a prefork mpm is a mystery to me.
now, I don't really understand this decision, but I'm sure there is a good reason for it. but I bring it up here because it seems like checking for perl threads may provide all the data you need to make the decision on whether full/limited module loading makes sense - it really depends on how prefork + threaded perl ends up behaving, which we will probably only really know after some experimentation.
however, if prefork (even with threaded perls, and thus interpreter pools) does perform better with maximal pre-loading, then what you need is probably something like Apache->mpm_is_threaded, which we can offer easily.
--Geoff
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
