https://bugs.kde.org/show_bug.cgi?id=498363
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to Pyx from comment #0)
> ... pin my SSD to 100% usage forever and eat up 300mb of memory.
Three possibilities here...
One that you've added/changed a large number of files. That should not be an
issue since the BTRFS bug was fixed (quite some time ago,
https://invent.kde.org/frameworks/baloo/-/merge_requests/131). However, if you
are using BTRFS, have not reindexed since then and your index is larger than
your RAM (as a rough indicator), then kill Baloo, purge and reindex.
Second, if you are I/O bound and Baloo is using *only* 300 MB is a bit strange.
When run under systemd, the unit file for Baloo rather strictly limits RAM use
to 512MB (you can check with "systemctl status --user kde-baloo"). That can be
low and Baloo ends up repeatedly re-reading info from the index rather than
having it "there", cached in memory. That I/O might be reads... but...
Third, if you've recently deleted a large number of files. Baloo doesn't batch
up deletes in the same way as it batches up indexing requests (it normally
indexed 40 files in a go and commits the results to the index). When you delete
files, they are removed from the index one by one which can be a lot of work.
Again, it might be worth looking at the size of the index (the file is under
~/.local/share/baloo)
--
You are receiving this mail because:
You are watching all bug changes.
