indeedeng/lsmtree

Question

Opened this issue · 0 comments

Hi, first at all compliment for this project! I found this library casually and i gave a look ... it is very well written and complex.
If there is a durable transaction with 10 elements i have to call flush when i commited. But this method for your opinion is good and it is performant? Using big memory block for every flush you save all the block also if the area changed is little? it is correct?