https://bugs.kde.org/show_bug.cgi?id=488739
Bug ID: 488739
Summary: plasma-systemmonitor itself becomes too resource
intensive
Classification: Applications
Product: plasma-systemmonitor
Version: 6.1.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: mark...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
Created attachment 170637
--> https://bugs.kde.org/attachment.cgi?id=170637&action=edit
Shows the cpu resource usage of plasma-monitor itself
SUMMARY
I'm not reporting a specific bug, rather the CPU usage of plasma-systemmonitor
itself has become so resource hungry that using it to see "which process makes
my cpu burn" became pointless as the act of monitoring makes the monitoring
itself high in CPU usage.
See the attached image for an example of resources usage. Here i'm showing the
same in plasma-systemmonitor and in top.
The irony. plasma-systemmonitor and top were running at the same time. top
barely even registers in resource usage! This does mean that system monitoring
can be done in a not so cpu intensive way.
Ideally plasma-systemmonitor itself barely registers in cpu usage.
All of this was run on Archlinux x86-64 with the latest plasma release (6.1.0
at the time).
--
You are receiving this mail because:
You are watching all bug changes.
