I have baloo activated to index my files in different locations on my hdd, but after any noticeable changes in the hierarchy of files/folders then after rebooting baloo indexer starts to index and consumes half of cpu use which slow down other apps like firefox and dolphin and writer. Normally an indexer should run in the background without any high priority to finish indexing all modified folders which means cpu usage for baloo should be limited to avoid slowing down the current important apps that are running at the same time. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-42-generic OS Type: 64-bit Processors: 2 × Pentium® Dual-Core CPU T4400 @ 2.20GHz Memory: 5.6 GiB of RAM
Created attachment 126494 [details] Baloo high cpu usage
*** Bug 423188 has been marked as a duplicate of this bug. ***
*** Bug 425160 has been marked as a duplicate of this bug. ***
*** Bug 406486 has been marked as a duplicate of this bug. ***
(In reply to medin from comment #0) > ... after any noticeable changes in the hierarchy of files/folders > KDE Frameworks Version: 5.67.0 ... Yes. After renaming a folder tree, baloo was busy and dolphin noticeably slow. I found it sometimes necessary to log out and back in again. I think this behaviour is now "well fixed". Have a look at Bug 431664. This was written at the time of 5.78.0, referring to a fix done in 5.68.0. You'd need to "balooctl purge" the index and let baloo reindex from scratch. You don't say how many files you're indexing. With a lot of files and a dual core machine you'd notice the impact while the index was being rebuilt.