db: cache chain config in local kv::api #2798
Open
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
battlmonstr
force-pushed
the
pr/chain_config_cache
branch
from
52872de to
bd0e9ba
Compare
battlmonstr
force-pushed
the
pr/chain_config_cache
branch
2 times, most recently
from
de8853e to
6dd33c2
Compare
battlmonstr
force-pushed
the
pr/chain_config_cache
branch
from
6dd33c2 to
57237ce
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.
It is possible to cache the ChainConfig structure after reading it from mdbx, because it is immutable after the node has started.
This optimization shaves off 0,6% of total time during stress_test_eth_call_20M.tar.