Let's start from the beginning.
How are you going to detect how much memory a thread consumes?
no ideas
There is an old patch in the Zends PAT directory http://devzone.zend.com/content/patch/pat38.txt (it reads the /proc/pid though or
fallbacks to getrusage).
Have used this for quite a time in past but got to conclusion that just finetuning the max_requests setting works better even with
leaking code/extensions as the small leaks get _fixed_ when the child restarts but for the big ones (like imagemagick used to be)
killing the child each time is rarely any solution either.
Of course the option to make the childs permanent and from time to time check
the memusage could be usefull.
rr
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
