Geoffrey Young wrote:
[...]
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.

The same way it handles pools under threaded mpm. Interpreter pools have nothing to do with threads. Under both mpm you create several interpreters under the same process and then you use them, regardless whether you are running in the process w/o threads or w/ threads.


now, I don't really understand this decision, but I'm sure there is a good reason for it.

I did ask doug about it some time ago, thinking that it was a bug. He said that it was by design. For example you can have several developers using the same mp2 server with their own VirtualHost having a different @INC, so that they can develop modules with the same names.


So far I understand that this is mostly useful for development. It doesn't seem to be very practical for production.

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.

It's not the thing you want to do based on the above explanation. Regardless of having perl w/ ithreads, you want to preload things only for non-threaded mpm.


But again, what Liz wants to do, she needs more tools, in order to preload things only at the server startup.

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.

Yes.



__________________________________________________________________ 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


-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html



Reply via email to