> Preloading has nothing todo with shared memory. The idea is to load as much
> as possible in the parent process. Now, when a child is forked, all childs
> have the same modules loaded. Since Unix only copies the memory when a write
> to a memory loactaion takes place, the preloaded modules will actually share
> the same memory location, as long as they not write to the memory.
Gerald, are you sure that it works that way? If it's, why top() reports a
bigger size of the shared memory when more modules were preloaded at the
server startup?
I know that the main idea behind the shared memory is for dynamically
linked apps, which share freezed text memory segments and not the heap
memory Perl uses for its compiled code.
Memory management gurus (Vivek? Frank?), will you please step in and
explain this issue once and forever? There is a lot of confusion goes
around the "sharing" term. Thanks a million!
_______________________________________________________________________
Stas Bekman mailto:[EMAIL PROTECTED] www.singlesheaven.com/stas
Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC
www.apache.org & www.perl.com == www.modperl.com || perl.apache.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com
