perf: put dirties in cache and move to database when commit #30
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
FletcherMan
changed the title
FletcherMan
changed the title
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.
Descriptions
It is an optimization for handling the dirty data based on zk trie.
In current zktrie implementation, the dirty data produced by transactions will be directly stored in
trie.databasewhen executingIntermediateRootfunction, which means these data will be flushed into diskDB eventually, even the corresponding block is not confirmed yet.We introduced a cache map to store the dirties produced during the txs execution. And the cache will be flushed to database only when the trie is determined to be commit