Speeding up indexing by exploiting temporal locality of UTXO use. #703
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
Working on issue ordinals#371 Most UTXOs are short-lived so to speed up indexing, we introduce an in-memory HashMap that collects all outpoint-to-ordinal-range mappings since the last DB commit, and serves as a cache. On mainnet this avoids around 80% of the writes to the redb BTree and results in a 2x speedup for indexing at the expense of slightly higher RAM usage. Also introduces more detailed logging and time keeping.
veryordinally
force-pushed
the
issue-371-locality
branch
from
908651a
to
dbbf80f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Working on issue #371
Most UTXOs are short-lived so to speed up indexing, we introduce an in-memory HashMap that collects all outpoint-to-ordinal-range mappings since the last DB commit, and serves as a cache. On mainnet this avoids around 80% of the writes to the redb BTree and results in a 2x speedup for indexing at the expense of slightly higher RAM usage.
Also introduces more detailed logging and time keeping.
Also, this includes #702, not sure how to pull these two apart.