Posted Apr 19, 2007 14:58 UTC (Thu) by AnswerGuy
Parent article: ELC: How much memory are applications really using?
Having written an internal guide to "Understanding Memory Utilization" for
my current employer, developed courseware and taught numerous courses in advanced Linux systems administation (including sections on vmstat, top, slaptop etc) and having found, during my career as a consultant, many occasions to explain to programmers: "No, these systems don't need more memory and they are NOT swapping no matter what that top and free seem to be saying" ... with all that under my belt I can say:
I'm so looking forward to having this incorporate into the mainstream. I
can scarcely imagine how much easier it will be to administer systems and
monitor memory capacity issues with these.
(Of course we'll still strive for a simple rule of thumb ... if you don't
have about half of your RAM available for caching ... you could probably
use a bit more in the system). :)
(I'm also looking forward to seeing the merge of I/O stats and atop compatible kernel patches that allow us to find the I/O hogs on a per process and per channel basis; that's been a, by far, the worst gap in
the performance analysis arsenal for Linux).
to post comments)