After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 432892 - the "CPU History" graph info is unclear
the "CPU History" graph info is unclear
Status: RESOLVED DUPLICATE of bug 530268
Product: system-monitor
Classification: Core
Component: resources
2.18.x
Other Linux
: Normal enhancement
: ---
Assigned To: System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-24 09:20 UTC by Sebastien Bacher
Modified: 2011-11-15 15:51 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Sebastien Bacher 2007-04-24 09:20:05 UTC
The bug has been opened on https://bugs.launchpad.net/bugs/109356

"Binary package hint: gnome-system-monitor

Hi! This report is about System Monitor 2.18.1.1, running on Ubuntu Feisty. It would be a nice fix for Gutsy.

Currently the CPU History graph in the System Monitor is a nice tool for a quick estimate of the current CPU usage, but only for a very rough estimate. The main problem is that the units are not very clear: the time axis is not marked at all, so I can at most estimate how long a spike took; the height is marked in percent -- but doesn't mention exactly of what.

I'm using Ubuntu on a Centrino Duo laptop, which can change the frequency of each processor according to several factors. (I'm not sure if it can scale each core separately, though. The factors I know are load and whether or not I'm plugged in, there may be some other heuristics.)

All this means that xy % processor usage can mean very different things in terms of how much work the computer is doing. At the very least, the legend below the graph -- [color] CPU#: ##.# % -- should be changed to something like [color] CPU#: ##.# % usage (at ## GHz) -- though this doesn't fix the graph. Maybe a different line (different shade or dotted) could indicate the frequency of the processor."
Comment 1 Robert Roth 2011-11-15 15:51:30 UTC
Thanks for the bug report. As the time axis already shows seconds, and the other issue is the CPU usage not showing what is the current CPU frequency selected, and there is another report about that in our bug tracking system, I am marking this as a duplicate of that issue. Feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 530268 ***