3 ms·
A quick practical answer is to use htop and look at the memory bar. * Green = resident memory used (probably what you want most of the time) * Blue = buffers
by rdtsc 13y ago
A quick practical answer is to use htop and look at the memory bar.
* Green = resident memory used (probably what you want most of the time)
* Blue = buffers
* Yellow = cache
- ChuckMcM 13y ago+1 for htop, it not only shows excellent memory stats in an easy to absorb way but it also shows CPU cores usage. Definitely one of my "wtf is going on?" tools.
- hisham_hm 13y agohtop author here. It was nice seeing the table in the article with the memory split in three colors and thinking "well, but that's how I already split it in htop, isn't it?". The "Linux calls it" column should probably be called "top calls it"...
- rdtsc 13y agoThank you for writing htop, it is very useful tool. I just about fell off my chair when I realized I could click with my mouse on the columns to sort them!
- gregf 13y agoI always forget the key bindings for this, you just changed my life!
- rdtsc 13y agoIt was accidental too. I was just showing my coworker something and I have a bad habit of highlighting stuff I am reading and randomly clicking on text, and I noticed that column was selected to be sorted. It blew my mind, this was in an SSH session logged into a remote server.
- sciurus 13y agoI'll give a pitch for atop as well. Here's a screenshot of it showing systemwide and per-process memory information: http://www.atoptool.nl/images/screenshots/memory.png http://www.atoptool.nl/images/screenshots/memory.png Here's a case study of using it to observe a memory leak: http://www.atoptool.nl/download/case_leakage.pdf http://www.atoptool.nl/download/case_leakage.pdf