https://bugs.kde.org/show_bug.cgi?id=461256
--- Comment #11 from tagwer...@innerjoin.org --- (In reply to Alberto Salvia Novella from comment #10) > It doesn't seem to be CPU Cores, RAM or IO saturation. What happens is that > when "baloo_file" uses 25% of CPU, one core of four, the graphical interface > sees a drop in framerate. Like going from 120 to 15 permanently till > "baloo_file" stops. I had a go at installing a Manjaro system, just in case there is anything out of the ordinary with it, and did the test of creating 50,000 files. I ran it as a guest VM under KVM with similar number of CPU's and amount of RAM as your system and didn't hit any surprises. I didn't see any changes in frame rate (it was stable at 60 fps) but the setups are probably far too different to show anything. > This is probably related with the fact that APUs share memory between CPU, > GPU and RAM. So most likely some shared memory between those is saturated, > not in amount, but in frequency. Context switching. One alternative thought, assuming the slow down / speed up happens a little after baloo_file starts or stops working. Might the CPU throttle back when it has to work hard and heats up? (See Bug 453968) -- You are receiving this mail because: You are watching all bug changes.
