https://bugs.kde.org/show_bug.cgi?id=404057
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |FIXED
--- Comment #45 from tagwer...@innerjoin.org ---
(In reply to Kai Krakow from comment #44)
> ... `MemoryHigh=512M` is quite aggressive. It can lead to swap storms
> and cache thrashing of baloo under memory pressure ...
> ...
> I personally used `MemoryHigh=2G` to fix this for my system...
Yes, there's been a handful of bug reports where I've "blamed" the 512M limit.
I tentatively recommend "MemoryHigh=25%". I don't suppose many people run on
systems with 2G RAM (even as VM's) and having a percentage means Baloo gets a
lot more room to breath on systems with 8G.
I think "MemoryHigh=40%" is still quite reasonable and I would also include a
"MemorySwapMax=0" to forestall swapping (which does seem to cause problems)
> No objections, it makes sense.
Will close then...
--
You are receiving this mail because:
You are watching all bug changes.
