https://bugs.openldap.org/show_bug.cgi?id=10072
--- Comment #2 from Tagwerk tagwerk19.openldap@innerjoin.org --- (In reply to Howard Chu from comment #1)
... Such a feature makes no sense, since LMDB automatically flushes dirty pages to disk when transactions exceed a particular threshold ...
I started following this issue with:
https://bugs.kde.org/show_bug.cgi?id=394750
It is quite a torture test for baloo - with large transactions and constrained RAM, that baloo starts using swap and the process is killed "OOM" when the swap is exhausted.
The protections to avoid TXN_FULL are most probably needed but baloo hits the systemd memory caps, OoM protections or starts swapping before it gets close to a TXN_FULL.
It would make *real* sense to be able to avoid this.