This repository has been archived by the owner on Feb 6, 2025. It is now read-only.
feat: state cache for execution #153
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
forcodedancing
force-pushed
the
execution_cache_1.0.7
branch
3 times, most recently
from
7030558 to
54e8451
Compare
forcodedancing
force-pushed
the
execution_cache_1.0.7
branch
3 times, most recently
from
cf70bc4 to
ad78a8a
Compare
forcodedancing
force-pushed
the
execution_cache_1.0.7
branch
from
ad78a8a to
1d64a40
Compare
unclezoro
reviewed
Oct 11, 2024
unclezoro
reviewed
Oct 11, 2024
unclezoro
reviewed
Oct 24, 2024
unclezoro
approved these changes
Oct 24, 2024
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.
Description
Try to improve the speed of execution.
Use the flag
optimize.enable-execution-cacheto enable the cache for execution.Rationale
Implement a layer of cache for db access.
Test results:
Compared the execution time of the original version and the cached version, for block range between (41932000, 41942000]. For each test the machine is rebooted (at the beginning it takes more time to execute) .
Cached version has shorter total execution time. The decrease of execution for every 100 blocks is about 15% ~ 20%.
Also tracked the cache hit rate for long-run (different block ranges).
Account hit rate is about 45%, and storage hit rate is about 30%.
Example
NA
Changes
Notable changes:
Potential Impacts