At 10:31 PM +0100 1/23/03, Juergen Boemmels wrote:
Which will generally be the case, I expect. Tell a sysadmin that they can reduce the memory footprint of mod_parrot by 50% by running a utility (that we provide in the parrot kit) over the library and I expect you'll see smoke from the keyboard as he/she whips off the command at supersonic speeds... :)Dave Mitchell <[EMAIL PROTECTED]> writes:On Thu, Jan 23, 2003 at 09:21:45PM +0100, Juergen Boemmels wrote: > My current idea for the in memory format of the bytecode is this: I would strongly urge any file-based byte-code format to arranged in such a way that it (or most of it) can simply be mmap-ed in (RO), analogously to executables. 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.This might be possible if the byteorder, wordsize, defaultencoding etc. are the same in the file on disk and the host.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
