Bug 442509

Summary: Default CPU graph defies physics (total usage more than 100%)
Product: [Applications] plasma-systemmonitor Reporter: Marcello Massaro <dev>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ahiemstra, kde, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.22.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: CPU usage graph scale, showing more than 100% total CPU usage.

Description Marcello Massaro 2021-09-16 09:35:34 UTC
Created attachment 141587 [details]
CPU usage graph scale, showing more than 100% total CPU usage.

The default interface of the new System Monitor (I bet) simply sums the individual core usage percentages and plots them. This means that the scale on the y-axis goes up to 400% (since my CPU has 4 cores), which makes no sense. I think somewhere there's a "divided by ncores" missing in the code. :)
Comment 1 David Edmundson 2021-09-16 09:39:49 UTC
There's not.

It is a stacked view, and every core can go up 100%, then you will reach a sum that is 400% of the value of a single core.

You can toggle stacked view, or choose to show only an overall CPU.
Comment 2 Marcello Massaro 2021-09-16 10:11:06 UTC
OK, then maybe it makes more sense to modify the default title to "CPU cores", because simply "CPU" makes me think of something else (where it's wrong to put 400%). Better even to simply hide the y-axis labels.

I know I can change the title by myself (the whole configurability of this thing is awesome). This is now more a problem of how DEFAULTS are presented and setup. And by default, it just looks weird/counterintuitive (well, to me).
Comment 3 David Edmundson 2021-09-16 10:15:00 UTC
We need to do something, it's been asked by enough people that we definitely have a UI problem.

IMHO we should just show total CPU, there's no usable data in seeing cores.
Comment 4 Nate Graham 2023-04-03 20:28:43 UTC

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