On Mon, 2006-03-13 at 15:11 -0500, Matt Adams wrote: > One thing we've discovered is that the Apache children appear to be > sharing almost no memory. In fact, out of an average process size of > 34MB, 26 of those megabytes are marked as writeable/private and only 72K > appears to be shared between these processes.
There's really almost no way to tell how much memory a process is truly using. The things that we thought worked on Linux were proven not to work much at all, since the kernel doesn't attempt to track copy-on-write. One thing you can rely on is the report of how much total RAM is left on your system, and how much is used for buffers and cache (meaning it could be used for your app). Another approach is to see if the Linux::Smaps module will work for you. > I have utilized the startup.pl file and included most of the modules we > are using in the mod_perl web app but all that has appeared to do is > cause the Apache children to inherit those modules at time of forking > and thus cause the Apache children to start at 34MB instead of the 7 or > so MB that they were starting at prior to the use of startup.pl. None > of those modules included in startup.pl appear to affect the size of the > processes' shared memory. This actually is probably improving things for you. You're just being misled by using the wrong approach to measure it. - Perrin ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Maypole-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-users
