https://bugs.kde.org/show_bug.cgi?id=440417
--- Comment #5 from lemaitre <kde.acco...@lemaitre.re> --- (In reply to tagwerk19 from comment #4) > (In reply to lemaitre from comment #3) > > ... To be noted that the bug does not seem to appear at the file creation > > (even > > creating 10 000 files in one go), but at the update of the files ... > I noticed a difference between running > > touch testfile{00001..10000} > > a first time and repeating it. Dolphin worked a little harder but it was > still just a second or so of high CPU. > > Baloo spent a while catching up with changes and baloo_file_extractor had a > look at the "touched" files (in batches of 40). Nothing excessive though... > > Could there be an issue with large numbers of thumbnails? (How big is > .cache/thumbnails/normal?) I disabled baloo, because it was too power hungry. The process that eats the CPU is dolphin, its main thread to be precise. Indeed, the .cache/thumbnails/normal was huge, more than 3 GB. So I deleted its content. It seemed have made a difference, but only if I don't refresh dolphin window. But if I open a folder with many files, refresh it with F5, and then touch every file from the terminal, I end up in the same high cpu load case as before. The .cache/thumbnails/normal grew to 17MB and stopped there, so no alarm on this side. As a sidenote, with 10'000 empty files in the folder, the refresh takes a few seconds. -- You are receiving this mail because: You are watching all bug changes.