https://bugs.kde.org/show_bug.cgi?id=492808
--- Comment #7 from tagwer...@innerjoin.org --- (In reply to Ellie from comment #6) > ... The overall system load was rather low, only the write I/O seems to have > been > maxed out to the point of all I/O terribly freezing up ... I think the "watch points" are if Baloo is taking all the RAM and squeezing out the rest of the system (the cgroups "cap" on memory usage prevents that), that Baloo is forced to swap (it's being asked to do too much given the memory it has), it is repeated indexing a log file or it was really given a big collection of files to index (wine or steam being cases in point). If you've killed Baloo, purged the index and are reindexing, you might see the behaviour resurface. One additional question, you are not using BTRFS? There were previously issues with it and Baloo, mainly affecting OpenSUSE and Fedora. They were fixed a year or so back but all the same it is prudent to ask.... > ... Given for how long it > was like that, I assume it must have continuously rewritten something in the > index or written way too much into a log, since the resulting index file was > around 1000x smaller than what I'm guessing the write load would have roughly > produced ... A bit stuck without knowing what was being indexed: what "balooctl monitor" or debugging would have shown. > ... I don't think openrc has any cgroups limit functionality, although I hope > baloo > wouldn't be written to entirely rely on that. Nevertheless, unless that limits > write throughput, it likely wouldn't have mattered here ... It depends. It would not have made a difference to the total writes, it might have affected when and how much swapping was happening. It probably would have avoided the slowdown of the system you were seeing... >From what I've been told, it's not particularly easy for a process to see what impact it is having on the system - whether it is using too much RAM, forcing the system to swap, or waiting too long for a write to complete. Baloo is exceptionally careful with CPU and backs off when you are doing anything on the system - you would see it indexing 40 files, writing the results to disc, waiting a second or so and repeating... > ... Since I deleted the index and baloo however, sort of in a panic I have to > admit, I'm not sure I can easily get it back to the previous state ... That's fully understood :-) -- You are receiving this mail because: You are watching all bug changes.
