https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #28 from Mark <mark...@gmail.com> --- There always has been a resource issue with ksysguard and plasma-systemmonitor! It's just much more notable in plasma-systemmonitor. Some people say the fix is to reduce the sampling rate, reading files or heck even throw in io_uring as a "solution". No. plasma-systemmonitor sucks up an easy 50% across all cores. That is in any tab. Look at btop (https://github.com/aristocratos/btop) for example. In it's options (General -> Update ms) set it to 500ms. That very much over the top (pun intended) system monitor ONLY sucks up ~3% at that setting. Before anyone even thinks: "ohh, I bet it uses io_uring for that"... No, it doesn't! It uses: - standard C++ ifstream - does NOT use smaps_rollup, instead seems to be getting that from each individual pid in the stat, statm and smaps file. Little difficult to figure out precisely without diving in deep. So something is very very very very wrong in plasma-systemmonitor for it to behave so bad that it takes up 50% on all cores. Sidenote. The plasma-systemmonitor cpu usage is erratic. I've seen it - just while writing this message! - consume just a few percentages all the way up to 50%... -- You are receiving this mail because: You are watching all bug changes.
