| Summary: | plasma-systemmonitor itself becomes too resource intensive | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Mark <markg85> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ahiemstra, nate, plasma-bugs |
| Priority: | NOR | ||
| Version: | 6.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Shows the cpu resource usage of plasma-monitor itself | ||
*** This bug has been marked as a duplicate of bug 434877 *** |
Created attachment 170637 [details] 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).