[kvdb-rocksdb] Use "pinned" gets to avoid allocations #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR uses the
get_pinned()
API to save an allocation when callingget()
.Using the benchmark from #275 there's no noticeable speedup, likely because the vast majority of time is spent in rocksdb so even halving the allocations on the rust side has no noticeable impact.
Also included are some minor cosmetic changes and the rename of
drop_column
toremove_last_column
to make users aware of what the code actually does.