No, i didn't preload the scripts - I'm not familiar with the
technique, and it seems like there's enough dynamic fvariable-writing
and storage of html values done in the scripts that large chunks would
be unfairly 'written' and cause duplication.  Its a bad system design
for this volume, it should be filesystem cached static files that
update on change.  We're working on that.  one project at a time.  :)

Skylos

On Fri, 14 Jan 2005 16:16:30 -0500, Michael Peters
<[EMAIL PROTECTED]> wrote:
> 
> Skylos wrote:
> 
> > Also, to compare, I work with an apache 1.3 site that has alot of cgi
> > perl script on it.  With the idea that shifting to mod_perl registry
> > mode would cause this site to go faster, I modified the configuration.
> >  And watched the system load average rapidly climb into the
> > multiple-hundreds!  Its a tilt of the hat to BSD that it didn't crash
> > right there.  But I was able to kill apache (-9 -9 -9!!) and restore
> > the cgi scripts to normal mod_cgi handling.  What happened?  Memory
> > usage.  Each copy of the apache had those big cgi scripts loaded in.
> > And this very busy server had ALOT of processes running
> > simultaneously.
> 
> Did you preload the those scripts at server start-up? This would change
> it so that instead of each apache child having it's own copy of each
> script they would have been placed in shared (copy-on-write) memory.
> 
> --
> Michael Peters
> Developer
> Plus Three, LP
> 
>

Reply via email to