On Thu, 8 Jan 2004, Zeev Suraski wrote: > Obviously we're talking about httpd children and not 1,000 > roots... Anyway, depending on the module, if there's any sort of RINIT > initialization, the CoW trick doesn't work very well and it consumes some > per-process memory. There's also the function table which is not shared > and will grow by a few dozen kilobytes thanks to the extra functions, which > is not shared across children. > > Note, my position at this point is that there's probably very little gain > in this as well, unless we can find a large number of modules with a > significant amount of functions, some of them maybe doing their own > per-request initialization, thus conserving a significant amount of > per-process memory. The list that Andi posted does not convince me that > this is the case.
Yeah, I am all for getting rid of or at least seriously reducing what is done in any RINITs. That is a clear win. I would even go as far as to say that anything that has an RINIT should not be compiled in by default. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
