In <[EMAIL PROTECTED]> on 05 Dec 2003, Cees Hek <[EMAIL PROTECTED]> wrote: > Using fork is expensive. It will use up as much memory as the > current child is already using, so you might as well just use the > current child to finished the processing.
In most OSes, fork just sets the memory to copy-on-write, makes another process table slot, .... It doesn't actually copy the memory, so the memory cost is small. In some cases (most notably Windows using Cygwin w/o copy-on-write semantics), fork is emulated by copy the parent's memory. In this case, the memory cost certainly is significant. -ccwf -- Charles C. Fu ,-- Founder ___ __ __. . ,-/-- Web i18n, LLC (_,(_,|/|/ / www.web-i18n.net ----' -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
