The only bright side I can see at the moment is that most people won't have 150 modules loaded. But 50 modules will scale bad enough.
Agree. Which is why I think you really will have to know what you're doing if you want to use mod_perl with a worker mpm.
This may be old news to some, but I wrote an article about this about two months ago on Perlmonks: Things you need to know before programming Perl ithreads.
http://www.perlmonks.org/index.pl?node_id=288022
So, in the worker mpm, you need to load as little as possible before cloning, and only load modules when they are really needed inside the thread. This is perpendicular to prefork mpm, where you want to load as much as possible beforehand.
One of my related projects is load.pm (on CPAN) which is an AutoLoader type module with a twist. It allows for a more flexible way of loading modules. It allows external control over whether a module will load subroutines on demand or all subroutines at once. In a worker mpm you would want on demand loading, for a prefork mpm you'd want it all at once.
As my plan for world domination, all core modules should use "load.pm", or the load.pm functionality should somehow become part of interpreter. I'd appreciate feedback whether this is a good idea, or just a delusion of grandeur on my part. ;-)
Liz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
