Baloo tries to index all the files on your machine to make searching files and their contents easier. However I have had many troubles in the past with Baloo. Mostly with it consuming 100% of my CPU and doing absolutely nothing, resulting in me needing to kill the process.
On my laptop I frequently mount a remote folder from my media server for file storage or accessing media. This caused Baloo to hang when it tried to index the massive amount of files in the mounted directory. Additionally if I didn't mount the folder it also seemed to hog the CPU without doing anything. The fix here was to tell Baloo to ignore the particular directory, then delete baloo's database and allowing to re-index. It seems to work fine now, although the initial re-indexing is CPU intensive.
To exclude a particular folder you can edit ~/.config/baloofilerc and add a line with the following (with the relevant folder of course)
Code:
exclude folders[$e]=$HOME/FolderA/
Then delete ~/.local/share/baloo which removes the database so baloo can start over fresh. You will have to issue
For changes to take effect.
If you just don't want to use baloo at all (which I do on my other computer), you can disable it with:
Code:
balooctl stop
balooctl disable
which is temporary I believe. You can also disable it altogether by editing ~/.config/baloofilerc and setting:
Code:
Indexing-Enabled=false
Which is under the basic settings tag.
Hope this helps