The BerkeleyDB module hasn't implemented
DB->Env's USE_SYSTEM_MEMORY FLAG yet,
but we've been using it (via tied hashes)
for caching SSI output. It's about 100
times faster than using IPC::Shareable,
and won't create shared memory segments
behind your back.
Unfortunately the eagle book's use
On Sun, 20 Aug 2000, Angela Focazio wrote:
> It seems very inefficient on memory to have each child process forms
> its own cache, so I was interested in creating a centralized cache that
> all of the child processes could dip into (actually forming a module
> that allows for I/O & control of
You might want to look into IPC::SharedCache or IPC::Shareable. These
modules cache variables in shared memory.
Angela Focazio wrote:
>
> It seems very inefficient on memory to have each child process forms
> its own cache, so I was interested in creating a centralized cache that
> all of the child processes could dip into (actually forming a module
> that allows for I/O & control of a centralized cach
