https://bugs.kde.org/show_bug.cgi?id=502641
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to Niklāvs Koļesņikovs from comment #4) > This is insane. Presumably Baloo project set that MemoryHigh=512M value, so, > if > it's known to be a problem, please raise it to a reasonable value. Previously there was no limit and the 512MB was a reaction to the problems that caused. Those problems correlated to trouble with BTRFS, where files were indexed multiple times and therefore the index grew dramatically. The two together caused havoc. > I don't know the nature of the Baloo cache The index is a memory mapped file, so "close to the metal". A record can be just pulled off disk and used so lookups are *fast*, but that means more work when indexing. I don't think Baloo can determine what pages are in memory, how many of them are clean, how many of them dirty. The systemd/cgroups limit applies external pressure on the memory and seems to work pretty well. In a way it is good to have something external to Baloo enforcing limits, it takes any arguments away from Baloo itself. I really agree that the default should be changed. I have been recommending MemoryHigh=25%, which would be no worse on a 2GB Guest VM and give far better headroom elsewhere. -- You are receiving this mail because: You are watching all bug changes.
