We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There seems to be an effort made to recycle the mergingIter.heap.items slice here:
mergingIter.heap.items
pebble/merging_iter.go
Lines 317 to 321 in 56834cb
This doesn't play well with the iterAlloc memory pooling:
iterAlloc
pebble/db.go
Lines 971 to 980 in 56834cb
That's because the mergingIter field is cleared before these structs are placed back into the iterAllocPool:
mergingIter
iterAllocPool
pebble/iterator.go
Lines 2330 to 2335 in 56834cb
As a result, I see 1 memory allocation in each call to (*DB).NewIterWithContext:
(*DB).NewIterWithContext
This may be working as intended. If so, feel free to close.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There seems to be an effort made to recycle the
mergingIter.heap.items
slice here:pebble/merging_iter.go
Lines 317 to 321 in 56834cb
This doesn't play well with the
iterAlloc
memory pooling:pebble/db.go
Lines 971 to 980 in 56834cb
That's because the
mergingIter
field is cleared before these structs are placed back into theiterAllocPool
:pebble/iterator.go
Lines 2330 to 2335 in 56834cb
As a result, I see 1 memory allocation in each call to
(*DB).NewIterWithContext
:This may be working as intended. If so, feel free to close.
The text was updated successfully, but these errors were encountered: