Avoid constantly triggering stageloop when using Engine API #4797
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
|
Side note: CL seems also to have improved syncing speed, probably because send out responses faster since we dont pass through the stageloop. i observed lighthouse going from 27.7 slots per second to 110 slots per seconds. |
|
I like it |
enriavil1
reviewed
Jul 23, 2022
yperbasis
reviewed
Jul 23, 2022
yperbasis
requested changes
Jul 23, 2022
yperbasis
requested changes
Jul 23, 2022
yperbasis
approved these changes
Jul 23, 2022
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.
Rationale
Moving all non-stagedsync dependent rpc answers outside stage_headers.go as pre-checks in eth_backend.go.
Motivations