Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Blockchain Sync Improvements: Chain Data & Pipeline #5415

Open
non-fungible-nelson opened this issue May 2, 2023 · 2 comments
Open

Blockchain Sync Improvements: Chain Data & Pipeline #5415

non-fungible-nelson opened this issue May 2, 2023 · 2 comments
Assignees
@jframe @siladu
Labels
epic ready Epic ready to be worked on syncing TeamChupa GH issues worked on by Chupacabara Team TeamGroot GH issues worked on by Groot Team
Milestone
2024 Q1 Besu team

Comments

@non-fungible-nelson
Copy link
Contributor

non-fungible-nelson commented May 2, 2023 •
edited
Loading

Description

Besu needs to be able to sync the chain data as quickly as possible. It also needs to be more aware of the state of the client (i.e. is the worldstate downloaded? Can I begin validator duties?) and differ or parallelize the chain download to improve the sync UX for Besu stakers and RPC providers.

Goals

  • Faster time from start to validating by differing and/or improving chain download
  • Refactor chain pipeline for post-Merge environment

Acceptance Criteria:

  • New pipeline strategy for chain-data
    • Download blockchain in the background (?) Use 8 seconds of free slot time for background download
    • Better post-Merge sync target based on the CL blocks and what we receive from the CL
    • If we have deposit logs (Teku), immediately start validating when worldstate download is complete

Considerations

  • Consider implications for private networks (leave fast unchanged, update snap)
    • auto-detect lock-step sync with CL, switch to optimistic head rather than relying on fcU
  • Peering for improving sync performance
@non-fungible-nelson non-fungible-nelson added epic TeamChupa GH issues worked on by Chupacabara Team labels May 2, 2023
@non-fungible-nelson
Copy link
Contributor Author

#5373 ref

Need to re-evaluate post-Merge sync strategy. Q3 perhaps...

@non-fungible-nelson non-fungible-nelson changed the title Backwards Sync Performance & Stability Improvements Post-Merge Sync Performance & Stability Improvements May 8, 2023
This was referenced May 30, 2023
Closed
Closed
@non-fungible-nelson
Copy link
Contributor Author

#5535 has more context

@non-fungible-nelson non-fungible-nelson changed the title Post-Merge Sync Performance & Stability Improvements Sync Performance & Stability Improvements Sep 26, 2023
@non-fungible-nelson non-fungible-nelson changed the title Sync Performance & Stability Improvements Blockchain Sync Performance Improvements Nov 9, 2023
@non-fungible-nelson non-fungible-nelson changed the title Blockchain Sync Performance Improvements Blockchain Sync Improvements: Chain Data & Pipeline Nov 13, 2023
@non-fungible-nelson non-fungible-nelson added the TeamGroot GH issues worked on by Groot Team label Nov 13, 2023
@macfarla macfarla added this to the 2024 Q1 Besu team milestone Feb 2, 2024
@siladu siladu self-assigned this Feb 21, 2024
@jframe jframe self-assigned this Feb 22, 2024
@non-fungible-nelson non-fungible-nelson added the in-progress Epic being worked on by a workstream label Feb 27, 2024
@non-fungible-nelson non-fungible-nelson added ready Epic ready to be worked on and removed in-progress Epic being worked on by a workstream labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jframe jframe

@siladu siladu

Labels
epic ready Epic ready to be worked on syncing TeamChupa GH issues worked on by Chupacabara Team TeamGroot GH issues worked on by Groot Team
Projects
None yet
Milestone
2024 Q1 Besu team
Development

No branches or pull requests
4 participants
@jframe @macfarla @siladu @non-fungible-nelson