https://bugs.kde.org/show_bug.cgi?id=493561
--- Comment #2 from Steve Vialle <stev...@runbox.com> --- After some mucking around, I take back the comments on GPU load. While it does make the situation worse, plasma-systemmonitor performance really just sucks in general, and the UI becomes unusable if there is significant CPU-time contention of any kind... i.e. the exact opposite of what one expects from a class of tool primarily used to diagnose performance problems. Add this one to the long list of bugs, jank and missing functionality, cross reference countless threads on reddit et al. and that big discuss thread that was locked because it was "causing stress"... And it quickly becomes apparent that pretty much everyone outside KDE/Plasma developers hates this thing, because it's demonstrably and consistently worse than ksysguard in every metric that actually matters to an end-user. To put this another way, for all the (ex)windows types around here these days: Compare performance of the Windows Task Manager... Go on, I dare you. Can we please, please return to shipping a system resource monitor that is fit for purpose? (*cough* https://github.com/zvova7890/ksysguard6). Ksysguard was the darling of many a power-user for over 15 years, and not only has it been deprecated in favour of something missing most of those "power-user" features, that replacement isn't even usable under the very situation where one might want a system resource monitor in the first place. If anyone has suggestions on making this thing usable when it matters, I'm all ears. Otherwise I think I'll just go write an ebuild for ksysguard6, because it's becoming abundantly clear that nobody here cares. Yes, I realise that with GPU contention (mostly) off the hook this report is probably yet another duplicate. At this point I don't care either. -- You are receiving this mail because: You are watching all bug changes.
