-
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
perf: better engine downloads #3584
Conversation
37a0ae2
to
f1a226b
Compare
Codecov Report
... and 8 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
with #3588 we can keep the threshold and finalized hash |
cool, I'll just revert these then but keep the other changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm module one question
Ok(Some(_)) => { | ||
// we're fully synced to the safe block | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this even reachable? under which conditions? should we still attempt to download the missing parent in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes we should still attempt to download, because if we set the threshold to 32 but only check the finalized tag here, then this branch is common.
we need to continue downloading, otherwise it would stall
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
extracts a fix from #3416 where downloading would stall because we're already synced to the state.finalized hash.
this also changes the target to the safe hash and decreases the pipeline threshold to 8 blocks