https://bugs.kde.org/show_bug.cgi?id=356357
--- Comment #2 from Vishesh Handa <m...@vhanda.in> --- (In reply to Riku Voipio from comment #1) > Created attachment 95923 [details] > disable sync to make baloo indexing less intrusive > > This patch made indexing unnoticeable in UI. As side effect, indexing is a > lot faster as it doesn't pause to sync all the time. I'm a little conflicted about this approach since when the index does get corrupted, it will be impossible for us to detect it. With our previous backend (xapian), we used to get lots of bug reports which were because of corrupted databases :( Perhaps the correct approach would be to refactor `baloo_file_extractor` so as to not perform a commit so frequently. We currently do it after a fixed 40 files. Perhaps it would make sense to try and estimate the amount of changes, and then do a commit when we reach the threshold. I'm not sure if I should keep this bug open or what. Specially since this is probably only a problem during first run. -- You are receiving this mail because: You are watching all bug changes.
