On 23 Jun 2000, David Hodgkinson wrote:
>
> Stas Bekman <[EMAIL PROTECTED]> writes:
>
> > > If you take a large script, throw it at Apache::Registry, then you'll
> > > be compiling the script every time the a diaghter respawns.
> > >
> > > If you have your script largely preloaded when Apache starts spawning
> > > daughters, then you don't have that overhead.
> >
> > That's wrong. The script won't be compiled until it will be used. When a
> > process gets spawned, it doesn't know what scripts/handlers it's going to
> > use if they are not preloaded. And if they are, they are shared.
>
> I'm being unclear.
>
> When I say "script", I mean a small piece of stub code that makes
> calls into modules, that contain the bulk of the code.
>
> These modules are then loaded in startup.pl, and are therefore
> precompiled.
>
> I'd made the jump beyond a single, monolithic ".pl".
>
> Are we getting closer?
I think it doesn't matter whether it's a script or a module.
BTW, I read somewhere at Apache performance notes at apache.org that when
the load is high Apache would pre-spawn childs first 2, then 4, then 8
etc. As long as the MaxClients is bigger than the number of processes that
are running at the given moment.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://perl.org http://stason.org/TULARC
http://singlesheaven.com http://perlmonth.com http://sourcegarden.org
