When running balooctl index/clear with a lot of files it uses a lot of memory because transaction to DB is committed only at the end preventing lmdb to reclaim memory thus making memory use to only grow.
For example running balooctl index ./* on a folder with ~650 files made baloo to use 9GiB of RAM, m_pendingOperations.size() was 20M
Run balooctl index ./* on large folder and see it doesn't use that much memory.
| No Linters Available |
| No Unit Test Coverage |
| Buildable 9401 | |
| Build 9419: arc lint + arc unit |
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.
Do not create a new transaction per file, thats costly.
| src/tools/balooctl/main.cpp | ||
|---|---|---|
| 225 | You are discarding the write transaction here withouth calling commit() or abort() | |