This repository has been archived by the owner on Dec 1, 2024. It is now read-only.
Optimize db.clear() and db.iterator()
#784
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vweevers
commented
Sep 12, 2021
vweevers
changed the title
db.clear() by doing it nativelydb.clear() and db.iterator()
|
Relevant benchmarks are in Level/bench#29. |
Because this uses an iterator under the hood, it also refactors shared code between `db.iterator()` and `db.clear()`.
By using `emplace_back()`, reusing the `std::vector` cache between `iterator.next()` calls, and not advancing the iterator prematurely. That last one only matters for single reads (i.e. the first `next()` call or one made after seeking) and it doesn't improve performance compared to the previous release, just undoes a mistake in b815bea.
vweevers
force-pushed
the
optimize-clear
branch
from
56d19a2 to
9e146b5
Compare
|
Squashed. The test failure can be ignored: |
15 tasks
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #680. To be (partially) squashed before merge; I separated this into small refactoring commits for easier review.
By doing
db.clear()natively, without crossing the C++/JS boundary for every key, it's 27x faster. That's compared tomaster, shown as "baseline" in the graphs.After further refactoring and tweaking,
db.iterator()also became slightly faster. I also fixed an edge case where adb.close()would never call its callback if aiterator().next()was in progress and thatnext()call errored.