On Mon, 2006-05-01 at 10:56 -0700, Bill Moseley wrote: > Anyone familiar with pmap on linux?
No. The current best bet is Linux::Smaps, which Apache2::SizeLimit now uses. > I tend (and hope!) to believe GTop. Don't believe it. It's probably getting the same numbers you'd get from /proc/self/statm, and not accounting for copy-on-write well. There was a lot of discussion about this a few months back on the list. > I'm also using a mmapped cache file for sessions. That probably affects GTop, but I couldn't say for sure. > The other somewhat curious thing is that I'm not seeing any difference > in memory when I preload modules. Granted, I'm using Catalyst which > has a setup() method that brings in most code at module load time. > Do you think that accounts for the similar results below? Probably. Try dumping %INC at the end of your startup.pl when you don't preload. If the list is similar, that would account for it. One simple approach for memory tuning that avoids all of these issues is to just look at the output of "free." That will show you how much real memory is unused. If your tuning is working, that should be going up. - Perrin
