https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #40 from Riccardo Robecchi <sephiroth...@hotmail.it> --- (In reply to David Redondo from comment #39) > Just for the people ranting here: ksysguard and plasma-systemmonitor use the > same code to gather data about processes (libprocesscore from libksysguard) It is, however, true that KSysGuard consumes a lot less CPU resources, even if it is based on the same libraries. I have just tested this, and System Monitor consumes between two and three times the CPU. So while I think it is safe to say that there are indeed architectural issues in libksysguard, there are *more* issues specific to System Monitor which appear to compound over the library ones. To be specific, on my system (which hasn't changed since I opened this report three and a half years ago), System Monitor uses about 60% of one core, KSysGuard uses about 30%, BPyTop uses 5%. -- You are receiving this mail because: You are watching all bug changes.
