On Wed, 30 Aug 2000, Stas Bekman wrote:
> On Wed, 30 Aug 2000, Matt Sergeant wrote:
>
> > On Wed, 30 Aug 2000, Douglas Wilson wrote:
> >
> > > Forgive me if this is a stupid question, but I am rather
> > > ignorant in regards to mod_perl, and I'm curious about
> > > something.
> > >
> > > If you reload modules, does that increase the size of the
> > > forked children of the parent process? Or does just the
> > > parent reload, with the children having to die and respawn?
> >
> > It increases the size - you lose shared memory. But only on modules that
> > actually get reloaded.
> >
> > > Or do we care? :)
>
> We care a lot.
> http://perl.apache.org/guide/performance.html#Sharing_Memory
>
> But only in production. This module is used mostly for the development.
This module is actually designed so that it makes reasonable sense in
production too. The touch file thing makes sure that you can update
modules and make them live before you have scheduled downtime. I think
that's very useful for a live server, even if it does use a bit more RAM.
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
