34 ms·
This is just wrong. The Virtual Memory Size (VSZ as he calls it in the article) is not what is important. Measuring actual memory preasure and costs on modern
by pquerna 17y ago
This is just wrong.
The Virtual Memory Size (VSZ as he calls it in the article) is not what is important.
Measuring actual memory preasure and costs on modern Linux is pretty non-trivial, just look at this wiki page about Spam Assassin:
http://wiki.apache.org/spamassassin/TopSharedMemoryBug http://wiki.apache.org/spamassassin/TopSharedMemoryBug
He needs to measure the real size of a multi-process daemon like apache by using a script like the ps_mem.py:
http://www.pixelbeat.org/scripts/ps_mem.py http://www.pixelbeat.org/scripts/ps_mem.py
That can measure the real memory use of each daemon, and while I don't think the overall picture will change much, measuring VSZ is just inaccurate.
- davidw 17y ago> while I don't think the overall picture will change much, measuring VSZ is just inaccurate. I agree... which means that your "it's just wrong" comment is inaccurate too, because the general relationship of the various systems to one another, in terms of memory usage, is not likely to change much: it's obvious that one way or another, Rails doing complex dynamic stuff with templates is going to use more memory than nginx serving static files, with other things falling in between. Thank you, in any case, for the pointer to ps_mem.py. I am using a similar script, but it doesn't look at smaps, so I'll improve the one I have or use theirs.