! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
CPU usage monitor - Allow user to configure whether nice'd CPU usage is ignor...
Status:
RESOLVED: FIXED
Product:
Xfce4-hardware-monitor-plugin
Component:
General

Comments

Description alwayseverything 2017-10-10 07:49:14 CEST
Created attachment 7347 
Idle CPU usage

I found a strange behaviour when I ran a stress test called "mprime" that I downloaded some time ago (can't remember the source), namely that the xfce4-hwmonitor graph I configured to display the CPU usage of the two cores on my laptop did not respond at all to the stress test. I thought at first the program was buggy but the CPU usage was displayed in the "xfce task manager" and the core temperatures rise realistically when mprime is run. The xfce4-hwmonitor CPU graph has responded reasonably to other CPU loads such as running Firefox and opening/closing applications in the few months I've been using it.

I have three screenshots with "xfce task manager" configured to update once every 10 seconds. The graph at the bottom left of my desktop displays memory usage (orange) and cpu0 and cpu1 (green/blue) with text overlay (memory usage scrolls about about a tenth of the speed of the cpus). The graph at the top right to the left of the clock displays core0/1 temperature (yellow/red). The task manager is on the right. OS is Debian 9.1, xfce4-hwmonitor is installed from the .deb packages in the Debian archives.

The first screenshot shows slightly different measuring of CPU usage between xfce4-hwmonitor and xfce task manager... the laptop idles at about 10% CPU usage according to xfce4-hwmonitor and about 25% according to xfce task manager (the CPU is an AMD ultra-mobile core (bobcat) for netbooks/tablets.. very easily loaded).
Comment 1 alwayseverything 2017-10-10 07:52:14 CEST
Created attachment 7348 
mprime stress test not detected by xfce4-hwmonitor CPU graph
Comment 2 alwayseverything 2017-10-10 07:53:59 CEST
⇧ This is after running mprime for a bit, you can see the memory usage in the xfce4-hwmonitor graph, but the CPU curves do not respond... and the mprime burst is clear enough on the task manager.
Comment 3 alwayseverything 2017-10-10 07:56:09 CEST
Created attachment 7349 
Firefox

And here the load due to starting Firefox appears correctly on both xfce4-hwmonitor and the task manager.

If you want more diagnostic information you will need to tell me what commands or procedures to use as I'm ... slightly new to linux.
Comment 4 OmegaPhil 2017-10-11 18:31:31 CEST
Yep, its actually by design:

===============================

  // don't count in dnice to avoid always showing 100% with SETI@home and
  // similar applications running
  double res = double(dtotal - dnice - didle - diowait) / dtotal;

===============================

Its probably been that way for ~15 years. But, outside of the original programmer's preferences, if I used this monitor, I would at least want the option to report on ALL CPU usage... so I'll make this a feature request.
Comment 5 alwayseverything 2017-10-18 07:50:55 CEST
I see. A note on the main page explaining this feature/nuance of xfce4-hardware-monitor-plugin would probably suffice rather than adding "monitoring mprime/seti/etc" as an option.
Comment 6 OmegaPhil 2017-12-18 12:53:19 CET
This has been made configurable, I'm going to sit on it for a week to see if anything blows up before I make an official release.
Comment 7 OmegaPhil 2018-01-14 22:21:27 CET
Resolving as the new version has finally been released.

Bug #13910

Reported by:
alwayseverything
Reported on: 2017-10-10
Last modified on: 2018-01-14

People

Assignee:
OmegaPhil
CC List:
0 users

Version

Version:
unspecified

Attachments

Idle CPU usage (192.37 KB, image/jpeg)
2017-10-10 07:49 CEST , alwayseverything
no flags
mprime stress test not detected by xfce4-hwmonitor CPU graph (273.43 KB, image/jpeg)
2017-10-10 07:52 CEST , alwayseverything
no flags
Firefox (176.89 KB, image/jpeg)
2017-10-10 07:56 CEST , alwayseverything
no flags

Additional information