Precomputed hashx status #17
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
jackrobison
added
area: scribe
type: new feature
jackrobison
force-pushed
the
precomputed-hashx-status
branch
from
dac5279 to
e535bc6
Compare
-adds HashXStatusPrefixRow and HashXMempoolStatusPrefixRow column families
jackrobison
force-pushed
the
precomputed-hashx-status
branch
from
bf2eba0 to
8a2517a
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.
fixes #18
Adds the following column families:
HashXStatusPrefixRow: updated every block for all touched hashXsHashXMempoolStatusPrefixRow: updated with every refresh of mempool for all of the newly touched hashXs, cleared upon new block.This requires a database migration, it takes about 2 hours currently and will run automatically on first run from a version 7 database. To make this as fast as possible, make sure you have ~20gb of memory to use and run
scribewith theCACHE_ALL_TX_HASHESsetting on, without this setting ~4gb of ram is needed to migrate and it takes about 6 hours. The other services (scribe-hub and scribe-elastic-sync) don't need to be run while migrating, this saves on memory.After running the migration the cache_all_tx_hashes setting can be turned back off if desired.