https://bugs.kde.org/show_bug.cgi?id=460460
--- Comment #8 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #7)
> Slow jobs, shifting sands but maybe quieter waters...
I think a lot of dust has been kicked up and settled again in the last year
with:
https://invent.kde.org/frameworks/baloo/-/merge_requests/131
for KF6 and cherrypicked for KF5
https://invent.kde.org/frameworks/baloo/-/merge_requests/169
Together with:
https://invent.kde.org/frameworks/baloo/-/merge_requests/121
and
https://invent.kde.org/frameworks/baloo/-/merge_requests/148
The combination of the BTRFS fix and a "batching up" the baloo_file indexing
(like the baloo_file_extractor indexing was batched up) has made a lot of
difference elsewhere, particularly after a reboot.
The limits on memory use may make the indexing slower but they should mean that
indexing is less noticable (they do depend on the system running systemd). You
can stop baloo with:
$ systemctl --user stop kde-baloo
restart it with
$ systemctl --user start kde-baloo
See its status (and memory usage) with
$ systemctl --user status kde-baloo
and set up/edit an override to change the memory limits with
$ systemctl --user edit kde-baloo
The default limit is "MemoryHigh=512M", I tend to set a percentage such as
"MemoryHigh=25%"
I'll leave this open for now, but will set a "WaitingForInfo" at some point. No
rush...
--
You are receiving this mail because:
You are watching all bug changes.
