How much of a performance penalty does using Apache::SizeLimit have? Is there some
quantitative way of setting how often to check process size with the
"Apache::SizeLimit::CHECK_EVERY_N_REQUESTS = 10;" that results in the best performance?
Perrin Harkins wrote:
>
> I find Apache::SizeLimit is more effective than setting MaxRequests,
> because it won't kill off your well-behaved processes and thus spares
> you from extra process spawning, re-opening databases, etc.
>
> Make sure you don't set Apache::Resource to kill anything that's close
> to "normal". It does a harsh kill which can leave your users with a
> "document contains no data" and possibly mess up open dbm files, etc.
> It works well for catching runaways though.
>
> - Perrin
