From: Perrin H. <pe...@el...> - 2005-07-05 20:47:11
|
On Tue, 2005-07-05 at 23:30 +0300, Antti M V=C3=A4h=C3=A4kotam=C3=A4ki wr= ote: > it _still_ did all of the initializations twice=20 > with OI2. I haven't looked at how OI2's startup is organized, but this is probably fixable. Things called from PerlModule or PerlRequire will be run twice, but modules loaded inside of that will not. > I'm not sure if Apache::Reload works with OI2 very well since at least=20 > the Actions are cached & cloned by OI2. It might not if there is a lot of stuff happening that %INC doesn't know about. I still don't understand what you're saying FastCGI does though. Doesn't it also keep the interpreter alive in memory? > But to clarify the situation I'm talking about: It doesn't matter how=20 > many child processes you use with Apache, they all are forked from the=20 > main process and share almost all of their static memory with the paren= t=20 > process until the memory becomes dirty and has to be copied to the=20 > child's own pool. So even if you would run only one child process, you=20 > would still have to copy lots of memory on the first request. No, it's just a fork. Forking is very fast on linux and none of the memory gets copied until the pages are dirty. FastCGI forks too. - Perrin |