Bug 504994

Summary: Processes tab: Cannot tell if CPU usage column is scaled to 100%
Product: [Applications] plasma-systemmonitor Reporter: Alexander Potashev <aspotashev>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ahiemstra, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 6.3.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander Potashev 2025-05-29 23:27:30 UTC 
SUMMARY
Cannot tell if CPU usage column is scaled to 100%.

STEPS TO REPRODUCE
1. Look at the CPU column, it may say e.g. "5.0%"
2. 
3. 

OBSERVED RESULT
There's no way to tell of that means 5% of a CPU core or 5% of all CPU cores' capacity.

EXPECTED RESULT
Column should change name or add a note in every cell to indicate which of the options apply.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.14.0
Qt Version: 6.8.2
Kernel Version: 6.13.11-200.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.4 ГиБ of RAM
Graphics Processor 1: Intel® HD Graphics 530
Graphics Processor 2: NVIDIA GeForce GTX 960M

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-05-30 18:24:07 UTC 
There wouldn't necessarily be a way to tell if we changed it, either; if all processes displayed raw numbers rather than re-scaling them to 100%, then with low load where they didn't all add up to 100%, you still wouldn't be able to tell.

That said, I think the underlying problem here is that the numbers *are* re-scaled to 100%, which is not expected based on how other performance monitoring tools work, and also less useful than displaying a raw number.

For example, on my 16-core system, a process that displays 6% is actually maxing out an entire core and generating a substantial amount of heat and fan noise, but this rogue process won't be easily identifiable based on its CPU usage number.

Marking as a duplicate of Bug 449414, which tracks that.
Comment 2 Nate Graham 2025-05-30 18:25:06 UTC 

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