[ILUG] Apache child process footprint size
dave at compsoc.com
Fri Jan 5 14:19:21 GMT 2001
I've noticed that the memory footprint size of my apache child processes
varies based on the modules (and the way the modules are compiled) that i've loaded,
between 850k on some servers to 5.5mb on some other ones.
Is there anyway to find out how much each module is taking up, out of the
allocated space for that process?
I don't have mod_perl loaded on any of the servers (and i don't
really want to load it, although i reckon it might be the only way to find),
and i don't see anyway of getting this info from mod_status.
Last time i was playing around with this, I ended up commenting out modules,
and restarting apache and inspecting the footprint sizes each time, which is
just yucky. I'd prefer something a little more accurate :)
More information about the ILUG