>Any easy fixes to this? am I the first to find this? Am i missing
>something obvious? Perhaps having my own ChildRequest counter and
>dieing myself, but more randomly, is a better way?
If you're using mod_perl why not use the Apache::SizeLimit module instead of
the MaxChildRequests. AFAIK the only reason to have children kill
themselves and restart occassionally is to help offset any memory leaks in
the system...Apache::SizeLimit goes one step further...it will check a child
once every X requests seeing if the child is over a certain size in memory
(say 20M)...if it is...than it kills the child so the parent can spawn a
fresh one...otherwise it leaves the child as is....
Perhaps that would solve your problem? I use it at a check for children
over 10 megs every 50 requests and my servers run problemfree handling over
450 requests/sec each.
Sincerely,
Craig Vincent
