Bug 420148

Summary:	CPU Usage illegible on systems with large numbers of cores (e.g. Threadripper 3970x).
Product:	[Unmaintained] ksysguard	Reporter:	Steve Phelps <phelps.sg>
Component:	ksysguard	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	aspotashev, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.18.3
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	KSysGuard on Threadripper 3970x

Description Steve Phelps 2020-04-16 07:41:29 UTC

SUMMARY

The stock CPU usage tools such as System Monitor application and CPU load monitor widget do not produce legible output on systems with large number of cores.  Attached is a screenshot for KSysGuard with on a 32 core / 64 thread machine (Threadripper 3970x).


STEPS TO REPRODUCE
1. Install KUbuntu on a machine with a CPU with a high core count.
2. Run KSysGuard
3. Observe illegible display in 'System Load' tab

OBSERVED RESULT


EXPECTED RESULT

The display should be legible when the CPU has a large number of cores.  For example, there should be an option to show the total CPU usage as a single graph rather than showing usage by individual core.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KUbuntu 19.10 with backports enabled
(available in About System)
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Steve Phelps 2020-04-16 07:42:25 UTC

Created attachment 127590 [details]
KSysGuard on Threadripper 3970x

Comment 2 Alexander Potashev 2022-02-14 00:33:28 UTC

Ran into the same issue. In addition to the truncated percentage numbers, the tooltip (with a list of CPU load percentages) doesn't fit on screen vertically for a 96-thread CPU.

Comment 3 Christoph Cullmann 2024-09-23 20:59:57 UTC

ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!