https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #19 from Kai Krakow <k...@kaishome.de> --- After testing this a few days, with my patches it works flawlessly: No performance impact, krunner finds result immediately without thrashing the HDD, etc. That is, until you reboot: While with the patches it has no longer any perceived negative impact on desktop responsiveness, I see that Baloo still re-indexes all files. Steps to reproduce: 1. Start baloo for the first time (aka "remove your index") 2. Let it complete a full indexing cycle 3. Observe "balooctl indexSize" to see that there's no file left to index 4. Also observe that it has data in "ContentIndexingDB" 5. Reboot 6. Observe "balooctl indexSize" to see that "ContentIndexingDB" changed back to 0 bytes 7. Observe "balooctl status" and wait until it finished checking for missing files 8. Observe both commands to see how baloo now refills the ContentIndexingDB and adds all your files to the index again, resulting in double the amount of files after finishing the second run 9. From now on, on every reboot, the index only grows, constantly forgetting the ContentIndexDB and re-adding all files. This behavior is with and without my patches. @Martin Is this what you've seen, too? -- You are receiving this mail because: You are watching all bug changes.
