At 10:05 -0400 2001.10.02, Perrin Harkins wrote: >I tried that as well, but when I measured the memory used it didn't seem to >be a gain. The overrall size was bigger, and there wasn't significantly >more memory shared than before. I'm not sure why, but I figured it probably >meant that things were being shuffled around in memory causing writes to the >copy-on-write pages.
Well, our goal was primarily in speeding things up, not reducing memory use. Compiling and caching all those templates is time-consuming. Having them already right there when the user loads the first page is important for us, and it is faster, and less CPU-hungry, to compile them in the parent process than to compile them in each child on startup (not to mention that I never got PerlChildInitHandler to work with virtual hosts, so I had no good way to do it in the child anyway). -- Chris Nandor [EMAIL PROTECTED] http://pudge.net/ Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
