Hi all - > 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.
The above link mentions the memory benefits of having few perl intepreters among many threads e.g. if you have a mix of static and dynamic content. But it made me wonder what is the effect regarding the "spoonfeeding slow clients" scenario? In mp1-land I'd run a lightweight reverse proxy to send dynamic requests back to a heavy mod_perl server, where the heavy mod_perl process is freed up as soon as content is generated and the lightweight reverse proxy process feeds the data to a slow client. What happens in the same situation when running mp2 threaded MPM? Is there any penalty because the thread which has loaded the perl intepreter stays busy until all data is returned to the client, as compared to a thread which has not loaded an interpreter? Is the interpreter which has been loaded tied up until all the data is returned to the client, or is it freed as soon as content is generated? TIA, Larry -- 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
