Closed rsdy closed 2 years ago
Thanks for reporting this. I've briefly tested the scenario, and it indeed seems problematic. Actually, it is not a leak, instead, ebr
reclaims garbage instances way too slowly. I'll try to make memory reclaim faster..
It will take some time to fix the issue. Expediting memory reclamation is not as simple as I expected.
The fix speeds memory reclamation up by a factor of 3; not quite satisfactory, that it is the best that I can get in short time. Hope that it will help. => Will be included in 0.6.1.
more aggressive memory reclamation applied. => Will be included in 0.6.2.
Yet another node reclamation method will be implemented in 0.7.0.
It seems like
TreeIndex
will leak significant amounts of memory with large number of insertions. I'm trying to insert a few billion records into a TreeIndex, with periodically cleaning it, like so:I can observe the memory use keeps climbing even though i call
clear()
to try to control it.I'm using 0.6 for these tests.