https://bugs.kde.org/show_bug.cgi?id=487916
--- Comment #10 from tagwer...@innerjoin.org ---
(In reply to Alexander Patrakov from comment #9)
> I would like to add that limiting baloo to 512M by default is
> counter-productive on my desktop PC. With just 512M, it just causes
> unrelated pages to go to swap frequently ...
I tend to agree....
What I've seen is the system drops and rereads "clean" pages and you get a
shedload more reads. You also might be forcing large transactions (loads of
dirty pages) into swap.
> Raising the limit to 5120M resolves the swap-thrashing issue, but it's
> obviously not a good idea to give 1/3 of my memory to something not related
> to the primary purpose of this PC.
This is really a "pick your number", if you give Baloo more space it indexes
more quickly. The memory demands are when content indexing (initial indexing or
after a purge...) and you are in the middle of a large job...
When troubleshooting I keep a watch on the Memory line in:
systemctl --user status kde-baloo
You can stepwise reduce the MemoryHigh value, Baloo will try to live within
that limit when indexing and it will release the pages when it finishes (and
other bits of the system ask for space). You can see Memory Use and Peak in the
systemctl status
> ... as there is no "memory+swap"
> accounting by default, only "memory". This swap-thrashing affects other
> apps, such as firefox ...
No, you *really* *really* do not want to swap...
You can put a "MemorySwapMax=0" in the unit file, are you saying that this
won't work? Maybe I've only dealt with systems where it did work...
--
You are receiving this mail because:
You are watching all bug changes.
