[Bug 245293] KSysGuard RAM usage summary doesn't match the real time plot

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245293

Adriaan de Groot <adridg at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Works As Intended

--- Comment #2 from Adriaan de Groot <adridg at freebsd.org> ---
The default tabs are defined in (XML) files like `SystemLoad2.sgrd`. Assuming
you have a normally-installed ksysguard, you have a
`/usr/local/share/ksysguard/SystemLoad2.sgrd` from packages. Once you've run
ksysguard, a copy is made locally, in
`~/.local/share/ksysguard/SystemLoad2.sgrd`.

The contents of the "default" tab come from this file (similarly, there's a
processlist .sgrd file for the other standardized tab in ksysguard). This file
-- both in the package and probably your  local copy -- uses the sensor
*mem/physical/used* which is .. total physical memory used. The status bar
shows a different sensor value, namely *mem/physical/application*.

While I could change things in packaging -- e.g. adding a sensor, or changing
the two default ones -- that wouldn't help **you** because you already have a
copy of the file, and ksysguard defers to that one.

I'm going to attach an alternate `SystemLoad2.sgrd` file to this bug report.
You can copy it into your local area (overwrite the existing one while
ksysguard isn't running) and when you restart ksysguard you get a graph with
**three** lines, of which the first (blue-ish) matches the statusbar value and
which indicates more accurately how your applications are doing.

I'm a bit hesitant to push this to packaging or as default anywhere, because it
adds lines (perhaps visual noise) and because there's 3 sensors in the graph
now, you lose the ".. of XXX" additional information. You could always remove
the second line -- on FreeBSD you'll almost always have the *physical/used*
sensor maxed out, just because ZFS ARC will eat up everything you have left.
Then you don't see overall memory pressure though.

I'll close this issue shortly, and in the meantime point you to
https://bugs.kde.org/show_bug.cgi?id=404637 which asks that this default tab be
editable -- which it should be, since you have a local copy anyway.

-- 
You are receiving this mail because:
You are the assignee for the bug.