https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #26 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- Further update on performance - the indexer is still running. Frequently, content indexing will pause for many minutes at a time, during which baloo_file will use 100% CPU and write to disk continuously for the whole time. The number of indexed files seems to be going down slightly - maybe Baloo is responding badly to me deleting a directory where I built some software? Much more concerning is the total disk write. I started tracking with iotop when content indexing was about 50% complete (in terms of number of files), and I'm now 66% complete. In that time baloo_file has 505 GB of disk write, and baloo_file extractor has 71 GB of disk write. That's astounding for a content index that's "only" 8.4 GB. SMART says that my disk has 4.6 TB written in its entire history (about 8 months old), and only about 350 GB is in use on this partition right now. It's entirely possible that half of the total write to my SSD was done *today* by Baloo. Given this I will almost certainly have to leave it disabled in the long term due to concerns about preserving my disk. Happy to make another bug report for the disk write issue if needed. -- You are receiving this mail because: You are watching all bug changes.
