...creating a hash of words from a CR-delimited list of words. The hash winds up taking up a few megabytes of RAM, but it's absolutely never written to, so I figured it would be shared between the mod_perl processes. However, each process grows by a few megs...
What's the best way to get around this?
Depends on how you measure "bigger". Things like top will normally
show you the virtual set size ("VIRT"); this includes the shared
portion ("SHR") and will add up to more than the total core used if programs share memory. If you look up the shared portion for the
proc's, Does it grow if you use the hash? If so then the O/S is
sharing the hash until its written.
-- Steven Lembark 85-09 90th Street Workhorse Computing Woodhaven, NY 11421 [EMAIL PROTECTED] 1 888 359 3508