Bug 442308 - High CPU usage with network activity
Summary: High CPU usage with network activity
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-11 14:24 UTC by Eugene Shalygin
Modified: 2025-06-10 03:47 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
illustration (149.55 KB, image/png)
2021-09-11 14:24 UTC, Eugene Shalygin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Shalygin 2021-09-11 14:24:19 UTC
Created attachment 141477 [details]
illustration

Basically a duplicate of #414036 with very same problem: any network activity maxes out CPU usage of the monitor app, so that it eats up the whole CPU core.

STEPS TO REPRODUCE
1. Open system monitor
2. Got to the "Applications" tab
3. Initiate network activity

OBSERVED RESULT

The monitor app utilizes a full CPU core.



SOFTWARE/OS VERSIONS
Operating System: Gentoo
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.1-gentoo (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 31.3 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600
Comment 1 Eugene Shalygin 2021-09-11 14:27:45 UTC
For the illustration purposes the network activity columns are enabled in the screenshot, but CPU usage stays the same with the columns set to "hidden".
Comment 2 Patrick Silva 2021-09-11 15:27:03 UTC
Same thing on Arch Linux.

Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 3 Josh 2023-05-18 11:45:51 UTC
Still exists..  this is the reason i just never use this app.  i'll use btop before using this because of the outrageous cpu usage to have it open which really just defies the point..  I would much rather use it because it is rather well layed out  but the CPU usage for me is a deal breaker and its been that way for years now..    

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD A6-6310 APU with AMD Radeon R4 Graphics
Memory: 10.6 GiB of RAM
Graphics Processor: KABINI
Comment 4 John Kizer 2025-05-10 04:53:11 UTC
Hi - some targeted work has gone into reducing System Monitor's CPU usage (https://blogs.kde.org/2025/01/11/this-week-in-plasma-final-plasma-6.3-features/#notable-in-performance--technical) - could you please let us know if this issue remains in Plasma 6.3.5? Thanks!
Comment 5 Lastique 2025-05-11 15:08:54 UTC
(In reply to John Kizer from comment #4)
> Hi - some targeted work has gone into reducing System Monitor's CPU usage
> (https://blogs.kde.org/2025/01/11/this-week-in-plasma-final-plasma-6.3-
> features/#notable-in-performance--technical) - could you please let us know
> if this issue remains in Plasma 6.3.5? Thanks!

I won't be able to test until the fix is released in the next Kubuntu LTS.
Comment 6 Bug Janitor Service 2025-05-26 03:47:27 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2025-06-10 03:47:22 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.