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

Streamline Stage Management #8977

Closed
gakonst opened this issue Jun 20, 2024 · 2 comments
Closed

Streamline Stage Management #8977

gakonst opened this issue Jun 20, 2024 · 2 comments
Labels
A-cli Related to the reth CLI A-staged-sync Related to staged sync (pipelines and stages) C-enhancement New feature or request S-stale This issue/PR is stale and will close with no further activity

Comments

@gakonst
Copy link
Member

gakonst commented Jun 20, 2024 •
edited
Loading

Describe the feature

A common workflow for benchmarking is to set the transactions log at block K, state at block K - B, and reth stage run over that range. Another one would be to do the same but by running the reth-bench command and replaying engine API messages w/ the state root on to benchmark live GPS.

We need 2 things:

  • reth stage unwind --offline which would skip pruning the online stages, so that we can run this in a loop -- we'd prob want to drop MerkleUnwind here because it gets slow on larger ranges
  • reth download --from --to which would run bodies + headers stage together (I am realizing now that reth stage run headers is unimplemented...)

Additional context

No response
@gakonst gakonst added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels Jun 20, 2024
@onbjerg onbjerg mentioned this issue Jun 20, 2024
Merged
@emhane emhane added A-staged-sync Related to staged sync (pipelines and stages) A-cli Related to the reth CLI and removed S-needs-triage This issue needs to be labelled labels Jun 24, 2024
@Rjected Rjected mentioned this issue Jun 25, 2024
Merged
@github-actions GitHub Actions
Copy link
Contributor

This issue is stale because it has been open for 21 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label Jul 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-cli Related to the reth CLI A-staged-sync Related to staged sync (pipelines and stages) C-enhancement New feature or request S-stale This issue/PR is stale and will close with no further activity
Projects
Reth Tracker
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gakonst @emhane