https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #23 from Arjen Hiemstra <ahiems...@heimr.nl> --- A blocking read shouldn't be using CPU unless it's actually reading something. In this case, the CPU time spent by the read call is the time the kernel spends building smaps_rollup. I'd love a better solution for that but it's the interface we have. So far the only improvements I could think of is to spread out how many updates we run in a single "update" cycle and to generally reduce the number of times reading smaps_rollup runs. -- You are receiving this mail because: You are watching all bug changes.
