Baloo seems to be using a lot of memory and disk activity while indexing files. What settings are worth changing if I still want to search for files in KDE Plasma?
How can I make Baloo less demanding without losing file search?
Answers
Start with the File Search settings in Plasma. Try changing Data to index to File names only, then exclude folders you don't need searchable. That keeps filename search while avoiding more detailed indexing.
Large collections of PDFs or development files may be worth a closer look. The tradeoff is that filename-only indexing won't give you the same content and metadata search coverage.
Reply to this answer
Before changing everything, check whether Baloo is actually the process causing the slowdown. Look at its memory and disk activity, and see whether the activity settles after indexing. Heavy use during an indexing run doesn't necessarily mean it will stay that way.
If it keeps hammering the disk, narrow the indexed folders first. That makes it easier to see whether the settings helped.
Reply to this answer
If the index still seems stuck or faulty after changing the settings, rebuilding it is another option. On Plasma 6, balooctl6 has suspend, disable, purge and enable commands for stopping indexing, clearing the index and starting again.
Purging removes the existing index, so expect Baloo to index the included files again. Check the command's help on your system before running it, and leave manual deletion of the index directory as a separate last resort.
deckExileCount_3Q:
Set the exclusions before rebuilding, otherwise the new index may spend time on the same folders again.
Reply to this answer
Add your answer
Answers are reviewed before publication.
LANguestWithATrackpad:
Would excluding hidden folders be a reasonable next step?
CRTbeamAlignment_6F:
Yes, if you don't need to search them. Cache, trash, game data and development dependency folders are useful candidates, but check what you actually want indexed first.