On Mon, Oct 04, 1999 at 12:41:45PM +0200, Stas Bekman wrote:
> > 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?
The word shared has multiple meanings. There's "shared memory" in the
sense of "SysV IPC" that the IPC::Shareable modules uses, then there's
also "shared memory pages" from forking or from loading shared objects.
How tools like ps and top show "memory usage" in these circumstances
can be a tricky issue.
Tim.
