https://bugs.kde.org/show_bug.cgi?id=424561
--- Comment #6 from David Edmundson <[email protected]> --- My reason for asking is I've turned things into a polling based API to an event-driven on-change API, which in theory should lower the CPU hit. Also by moving it to the backend rather than the UI we can apply something more sensible defaults like only fetching disks every few minutes, whereas CPU info is a lot more dynamic. So it was deliberately done to try and tackle this at the root for everyone. If there's any specific feedback on things no really working we can of course address that. -- You are receiving this mail because: You are watching all bug changes.
