https://bugs.kde.org/show_bug.cgi?id=449355
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #2 from tagwer...@innerjoin.org ---
There's been a fix about a year ago to limit (through systemd) the amount of
RAM Baloo can use:
https://invent.kde.org/frameworks/baloo/-/merge_requests/121
You might find Baloo is slower, as it tries to fit into the RAM its given, but
it will not grab so much that the rest of the system is affected.
There was a following patch:
https://invent.kde.org/frameworks/baloo/-/merge_requests/148
to make sure the initial scan for changes works within the restricted RAM.
These don't change anything when deleting a large number of files but it should
mean that Baloo's "catching up" in the background is not so noticeable.
Are you still haivng problems or is it OK to close this call?
--
You are receiving this mail because:
You are watching all bug changes.
