https://bugs.kde.org/show_bug.cgi?id=488645
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
Not many leads here are there...
My guess is that Baloo is working within its memory "cap" (it has a 512MB limit
defined in its systemd unit file) but the index has grown far too much. It will
struggle when reading - it will read scattered pages from the index, have to
repeatedly drop "clean" pages to read another ones, repeat and repeat. Means
loads of I/O.
When indexing you have this behaviour and a possibly a gradually increasing
number of dirty pages that cannot be dropped. That may push Baloo to start
swapping. That is *bad*.
This has to be a guess from your description. A 6GB index seems large. You
could see what
systemctl --user status kde-baloo
says and you could watch what's happening with I/O with iotop. Maybe try
increasing the 512MB limit (MemoryHigh) to something like 25% (it's a bit of a
'pick a number'), which should allow Baloo to make better use the RAM. As a
separate step, perhaps afterwards, you could set the MemorySwapMax to zero
(means that if you reach the limit, Baloo will be killed OOM rather than
running your system into the mud). You can edit these settings with:
systemctl --user edit kde-baloo
--
You are receiving this mail because:
You are watching all bug changes.
