Hey,
I like the idea of Apache::SizeLimit, to no longer worry about
setting MaxRequestsPerChild. That just seems smart, and might
get maximum usage out of each Apache child.
What I would like to see though is instead of killing the
child based on VmRSS on Linux, which seems to be the apparent
size of the process in virtual memory RAM, I would like to
kill it based on the amount of unshared RAM, which is ultimately
what we care about.
Here's why: any time I add a new module to the code base,
I am going to grow the RAM of all processes when I preload
them with PerlModule or use in startup.pl, but I DON'T CARE
about those, because they are shared, right? Problem is
I do care because I have to retweak the Apache::SizeLimit
every time my code base grows, because my RAM of each process
just grew at the post fork baseline.
I guess you could say, SO WHAT!, get over it, but it seems
like there should be a better way. * Dreamy *
-- Josh
