User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0
Build Identifier: 

Baloo file indexer is running since days at 100% CPU and I'm not sure if it
will ever finish.

Reproducible: Always

Steps to Reproduce:
1. Installed Tumbleweed from scratch on a brand new notebook (LG gram 2021
i7-1165G7)
2. Copied my home directory from my old laptop (approx. 700GB of data)
3. Watch baloo running at 100% CPU for days/weeks
Actual Results:  
Baloo seems to get slower and slower:

gram:~> balooctl status ; sleep 3600 ; balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Total files indexed: 3,683,585
Files waiting for content indexing: 160,364
Files failed to index: 0
Current size of index is 71.48 GiB
Baloo File Indexer is running
Indexer state: Indexing file content
Total files indexed: 3,683,065
Files waiting for content indexing: 159,844
Files failed to index: 0
Current size of index is 71.48 GiB

This means in one hour the number of files waiting to be indexed decreased only
by 520 (which would mean 7 seconds to add a single file to the index).
At this speed, I'd need to wait another 300 hours before the indexer completed
its job.


Expected Results:  
Indexing should complete *much* faster.