Brian Moon wrote:
Ilia Alshanetsky wrote:
Rather then terminating Apache request yourself, you can use universal
Apache configuration directives that allow you to restrict memory
utilization of an Apache process.
Hmmm, the ones I looked at seemed to prohibit a process from growing
above a certain size. Can you point me to them? I don't want to
prohibit a process from using what it needs (to a point). I need simply
need a child to terminate after it has gone above a certain threshold.
We found that the norm for our applications was 10-15MB. Usage above
that was the exception. Some applications (especially when they were
generating cache that had gone stale) would need more for a brief
period. I don't want to stop that.
I still think your best bet is to simply allow for the top watermark for
each of your processes and configure your machines with enough ram to
handle perhaps a smaller number of processes. Or fix your code to use
less if that high watermark is too high. Killing processes seems like a
very crude fix here.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
