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...)
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 thereth-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 rangesreth download --from --to
which would run bodies + headers stage together (I am realizing now thatreth stage run headers
is unimplemented...)Additional context
No response