Cockpit's memory usage graphs includes the cache but makes no distinction

[nekohayo]

I'm mostly interested in something close to gnome-system-monitor or htop's representation. Currently, Cockpit makes me believe that my server's RAM is full, but in practice half of it seems to be caching:

[dperpeet]

We have something like that in the details (click on Memory). The question is whether we should show that level of detail in the dashboard or not.
Or we could ignore cached memory in the dashboard overview, to keep it simple.

This needs some design @andreasn.
@mvollmer is currently working on changing the graphs.

[jmalacho]

if simplicity is the goal, Excluding 'cache' makes the most sense. Graphs like this are the reasons website like this(https://www.linuxatemyram.com/) even need to exist.

[garrett]

PRs #10101 and #10282 reworked the memory and its display.

Calculations have been redone, cached RAM has been de-emphesized on the details page and omitted from the overview, and swap has been split out into its own area on the top on both.

(Our design doc is @ https://github.com/cockpit-project/cockpit/wiki/Feature:-Memory-graphs)

As of today, Cockpit's memory reporting now looks like this in overview:

And like this in details:

Oh, and we did happen to base the new calculations on https://linuxatemyram.com/ 😉