Memtable memory usage causes OOM

I believe this is because the benchmark write tool creates long running iterators and these iterators hold the ref to the memtables for a long time. @ahsan also pointed out the issue is because we have a defer and that defer is not executed (we don’t return from the function).

@ahsan is running the benchmark write tool with disabled iterators to confirm our theory.

1 Like