https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #59 from tagwer...@innerjoin.org --- (In reply to Oded Arbel from comment #58) > Memory: 638.2M (high: 512.0M available: 0B peak: 656.2M) That makes it pretty clear... Baloo has been trying *long* and *hard* to get extra memory. The limit is soft limit (MemoryHigh rather than MemoryMax) so the system does begrudgingly allocate more but with steadily increasing delay. I've not seen Baloo ever manage to get hold of 638M RAM! I think in this case, you will need to override the limit, try "systemctl --user edit kde-baloo" as per Bug 502641 > ... It's mostly baloo_file_extractor, with baloo_file > taking only about 100MB. monitor still says "Idle" and status says ... That bit I don't understand - but I'm not sure how the monitor checks whether the extractor running. > 40% of system RAM for the background file indexer? That seems atrocious to me. You are seeing an edge case I think. If you get baloo_file_extractor to finish, it will release the memory it's using. You are trading space for time - or the Baloo design is. You have 5 million files, try asking for "baloosearch the | wc" and see how many hits you get and long it takes (and worth trying it more than once) and compare to your favourite grep (again try it more than once). There is an issue with baloo_file when cleaning up records for deleted files, there is room for improvement there.... > If you mean "dropped" as in goes to swap, then that's no good No, Baloo reads pages from the database when, say, it is looking to see which files contain the term. If it doesn't modify them they are still "clean" and can be dropped (forgotten) to make way for another page it needs. If it does need that first page again it rereads it from the index. So, when memory gets tight, you see a growing number of reads from the index and that can dominate the I/O. > ... it costs battery life and available time off AC ... Content indexing is paused when on battery, baloo_file stops feeding batches of files to the extractor when on battery (assuming you've got power management working). If the extractor is in the middle of indexing as in your case, it is not killed. -- You are receiving this mail because: You are watching all bug changes.
