https://bugs.kde.org/show_bug.cgi?id=394750
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED |NEEDSINFO
--- Comment #17 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #13)
> I think there is something to be fixed here...
>
> When baloo is indexing content it does it with batches of files
> (40 files, then the next 40 and so on) and commit the results after
> each. It would make sense to batch the initial indexing, something
> like a commit every 15 seconds perhaps. That would also allow people
> to see that something was happening with "balooctl status"
That's been done, there's been a patch to limit memory use with
systemd/cgroups:
https://invent.kde.org/frameworks/baloo/-/merge_requests/121
Together with a fix speculated about above, to commit regularly during the
initial indexing
https://invent.kde.org/frameworks/baloo/-/merge_requests/148
I'll leave this "Waiting for Info" but I think it can probably be closed...
--
You are receiving this mail because:
You are watching all bug changes.
