https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #10 from Arjen Hiemstra <ahiems...@heimr.nl> --- In that case it's 50% of one core, which is not different from what mine does. It also means that this is not going to be fixed any time soon, if at all. The problem lies with the complete lack of a kernel API[1] for the statistics that we query, apart from the text files in /proc. This means that every update we have to read the entire /proc directory to determine if there are new processes or if processes have gone away, then for each of these directories read a bunch of text files, parse them and convert that to something that we can use to display data. Moreover, these files are not real files but can potentially do stuff behind our back to provide the text data. One example here is /proc/PID/smaps_rollup which will actually go through a process' memory pages when it is opened and which is one part of the fairly large amount of CPU usage. [1]: There is actually a kernel interface to get basic process information over netlink, but it has been declared unsafe and can only be accessed by root. -- You are receiving this mail because: You are watching all bug changes.
