https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #29 from tagwer...@innerjoin.org --- (In reply to Adam Fontenot from comment #26) > ... In that time baloo_file has 505 GB of disk write, > and baloo_file extractor has 71 GB of disk write ... Trying to get my mind round that... > ... maybe Baloo is responding badly to me deleting a directory where I built > some software? Yes, that could be the reason. Baloo_file_extractor batches up its work, baloo_file does it when looking for new/changed files, maybe not when responding to iNotify events and I think it commits file by file after deletes. I think there's an argument for increasing the "40 files" batch size for baloo_file_extractor, that would come with a little more memory use but cut down on the total writes. Stefan says that people think they know how Baloo works better than he does, the above is just from observation and guesswork :-) -- You are receiving this mail because: You are watching all bug changes.
