-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Erigon 3: Prune canonical markers - CanonicalHash
, HeaderNumber
from chaindata
#11634
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
Giulio2002
force-pushed
the
prune-markers
branch
from
August 16, 2024 22:18
8c7a5a6
to
a503e28
Compare
AskAlexSharov
approved these changes
Aug 18, 2024
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.
We prune
CanonicalHash
andHeaderNumber
inchaindata
. this leads to a -99% in these 2 tables and reduce their total size to 40 pages in TOTAL (from >500k pages).Benchmarks:
Is the RPC working for those ranges? Yes.
How does it work?
Query canonical hash from snapshots by:
viewHeaderByNumber
->header.Hash()
if db hit is missedQuery header number from snapshots by:
viewHeaderByHash
->header.Num64
if db hit is missed