Tom Schindl wrote:
Thanks Stas for the full explaination. Indeed I didn't know exactly what's really going on behind the scences. Thanks for your explaination I'm always learning something new when reading your answers.
Thanks :)
Still on the one hand I recognize what you're trying to tell me, on the other hand could you give me more information about how things like this could be accomplished or better the other wayround how could I prevent things like 1 thread with 10 perl-interpreters and vice versa if I don't want it?
You use interpreter pool size control directives: http://perl.apache.org/docs/2.0/user/config/config.html#Threads_Mode_Specific_Directives
You don't need to prevent anything. It's just that if your server uses very little modperl and mostly doing static requests, you can have just a few perl interpreters around (in the threaded mpm) and many more threads. The above link explains how to set a limit on the size of the pool.
I know we need to write some docs explaining the nuances, since I've done this more than once here on the list. But all that after mp2 is released.
-- __________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
