D19644: Reduce balooctl index/clear memory usage

Sat Mar 9 20:09:50 GMT 2019

davispuh added a comment.

  In D19644#428047 <https://phabricator.kde.org/D19644#428047>, @bruns wrote:

  > A transaction can not be split up, thats the reason it is a transaction ...

  It can and they must be split in a lot smaller transactions. Currently sometimes baloo uses way too big transactions which causes memory usage to spike.

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D19644

To: davispuh, dhaumann, bruns, ngraham
Cc: bruns, kde-frameworks-devel, #baloo, gennad, domson, ashaposhnikov, michaelh, astippich, spoorun, ngraham, abrahams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190309/cd6c4af3/attachment.html>