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 615250 - some applet hints contain raw value, some of them only percent.
some applet hints contain raw value, some of them only percent.
Status: RESOLVED INCOMPLETE
Product: system-monitor
Classification: Core
Component: general
git master
Other Linux
: Normal minor
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-09 06:15 UTC by Коренберг Марк
Modified: 2012-01-25 08:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Коренберг Марк 2010-04-09 06:15:12 UTC 
Now, information show in hints of the meters in system-monitor applet:

1. CPU load - percentage
2. Memory - percentage
3. Network load - MB/S
4. Swap - percentage
5. load average - by value
6. Hard drive - percentage.

I think, every hint should contain percentage and raw value for every meter.
Comment 1 Robert Roth 2012-01-03 20:46:05 UTC 
Showing the percentage and raw unit for each graph is problematic, because:
1: CPU usage is expressed in percentage, and as far as I know, when the 2400MHz CPU usage is at 10%, it's not 240MHz, so displaying raw units doesn't seem appropriate for me.
2,4: As the Memory and Swap are displayed on the same graph, but they often have different sizes, showing percentage seems to be the best to address this.
3 For the Network load showing percentage is problematic, as we don't know what's 100% network usage, we can't easily find the network bandwidth, there's another bug reported for this, see bug #614848.
5. For load averages, we could show the percentage (value*100) but there's no raw unit to display here neither.
6. Hard drive usage is shown both with raw value and percentage (e.g. Used : 20.6 GB 57%)

How do you think we could address these issues?
Comment 2 Robert Roth 2012-01-03 20:47:24 UTC 
Sorry, referenced the wrong bug, it should have been bug 626738.
Comment 3 Robert Roth 2012-01-25 08:02:47 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!