On Sat, Jan 25, 2003 at 10:04:37AM -0500, Jason Gloudon wrote: > On Thu, Jan 23, 2003 at 08:39:21PM +0000, Dave Mitchell wrote: > > > This means that a Perl server that relies on a lot of modules, and which > > forks for each connection (imagine a Perl-based web server), doesn't > > consume acres of swap space just to have an in-memory image per Perl > > process, of all the modules. > > Are you sure the swap space allocation isn't mostly attributable to the poor > locality in the Perl process's data structures ?
I was using swap space as a loose term to mean virutal memory consumption - ie that resource which necessitates buying more RAM and/or swap disks. The locality wasn't a proplem. -- A walk of a thousand miles begins with a single step... then continues for another 1,999,999 or so.
