As kjetilho proposed on IRC :


-- a healthy server will often use half its memory on this. if the
majority of the memory is spent on apps, something needs to be done. I suggest a "neutral" colour, like light blue.


-- this is usually small (~2%). the size is dependent on the number
of processes (each having their own page tables), and their size. not sure in what cases this gets large (10% or more). if it can be large, it needs a colour which stands out. purple?


-- only present when swap is enabled. this is physical pages which

have been swapped in, and have not changed since the swapin. they can be discarded without needing to write to swap.

should have a colour which makes the relation to swap (and cache?) apparent. should be stacked with swap. dark red?


-- slabs are used for many tables. a major contributor is dentries
and inodes. a large slab_cache is not problematic in itself, but can point to applications which do too many filesystem metadata operations. orange?


-- cache are pages from files which are clean and can be discarded. green?


-- buffers are dirty pages or pages without a backing store. yellow?


-- unused is good, but doesn't have to be highlighted if it is at the
top of the stack. I suggest to make it a transluscent colour, light grey or a very lightly tinged green (to match "cache").


-- swap is bad. make it stand out, and put it on top of the stack
(above unused) to make it visible as a mountain range. red!

inactive commited active vmalloc_used mapped

-- these can probably stay unchanged.

stacking order:

the mostly unchanging stats should be stacked at the bottom. this would be stuff like slab_cache and page_tables. to summarise:

page_tables (purple?) slab_cache (orange?) apps (light blue?) buffers (yellow?) cache (green?) unused (very light grey) swap_cache dark red swap bright red
Last modified at 2013-07-18T08:27:46+02:00 Last modified on 2013-07-18T08:27:46+02:00