in reply to Re: Time to write a "serious" http server in Perl?
in thread Time to write a "serious" http server in Perl?

Pre-fork: [...] Unfortunately Perl processes use too much memory to have large numbers of them.

Could you explain why this is a problem? At least on the operating systems that I have worked with, forked processes continue to use their parent's memory pages until they need to write to them (aka "copy-on-write"). So if the parent (master) process is designed to load all the big modules and stuff, the children should produce little overhead in memory.

Replies are listed 'Best First'.
Re^3: Time to write a "serious" http server in Perl?
by tilly (Archbishop) on Aug 11, 2008 at 14:04 UTC
    People do this. Unfortunately due to Perl's reference counting, in normal use you wind up writing to data that you're just accessing. So while you can preload lots of stuff, and it starts off shared, it doesn't stay shared.

    Again, this is not a theoretical problem. It is a real problem that people at high-volume mod_perl sites have been dealing with for years. And the solution is standard as well.