https://bugs.kde.org/show_bug.cgi?id=371889
--- Comment #18 from Enrico Tagliavini <enrico.tagliav...@gmail.com> --- Created attachment 102168 --> https://bugs.kde.org/attachment.cgi?id=102168&action=edit callgrind record of plasma shell (slow performance) I've run a profiling run with callgrind. I started it with valgrind --tool=callgrind --instr-atstart=no --callgrind-out-file=plasmashell-callgrind.out -- plasmashell --shut-up so the instrumentation was not on during the whole startup. I waited a couple of hours with two panels and something animating in the systray. Once the CPU usage was maximized I started the instrumentation and also started switching active window as fast I could by using the mouse between two. Then I stopped instrumentation and stopped valgrind. Oddly enough, while plasma uses a lot of CPU and is quite slower compared to a fresh start, the system performance was not dragged down as much. Usually the whole system feels slower when plasma starts using more resources, for example kwin animations are much slower. Firefox feels slower. Probably everything related to rendering feels slower. Likely valgrind just shuffling the conditions, but I thought I should mention it. -- You are receiving this mail because: You are watching all bug changes.
