https://bugs.kde.org/show_bug.cgi?id=438074
--- Comment #18 from tagwer...@innerjoin.org ---
(In reply to Frank Steinmetzger from comment #17)
> Indexer state: Suspended
I wonder what does that nowadays... There used to be a "balooctl suspend" but I
think that's been removed.
> ... constant read I/O of 150 MB/s for at least half an hour after login ...
and
> Current size of index is 18.22 GiB
Gut feeling here is that the systemd limits on RAM are cutting in on you, have
a look at what:
systemctl --user status kde-baloo
says. The unit file limits Baloo's RAM use to 512 MB. When Baloo hits that
limit it will drop clean pages from its cache so it can load others. You see
Baloo slow down and spend a *load* of time and energy reading.
My personal view is that 512 MB is somewhat strict, 50% works for me (together
with stopping Baloo using swap)
MemoryHigh=50%
MemorySwapMax=0
Watch out for indexing email files, particularly those encoded or with
attachments. For .eml files see Bug 460882; .mbox files can be absolutely
massive.
--
You are receiving this mail because:
You are watching all bug changes.
