-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
Longer epoch transition time since capella #5409
Comments
Found bug attempting to resolve this. Put up issue #5440 and am attempting to debug that to pull the historical data to run flamegraph and benchmarks for the pre-capella state on 4/1 |
@dapplion @tuyennhv On initial investigation it does not appear that the transitions should be taking significantly longer post capella. The full transition is actually testing at 2% faster than pre-merge. There are some inner functions that are running much hotter but the overall speed doesn't speak to the 700-900ms jump. Before Capella (slot 6123583):
After Capella (slot 6260415):
Diff Between Runs
|
@matthewkeil got it! Thanks for looking into this. Closing issue since them it's likely caused for other factors on hardware. We can revisit latter if we have more evidence |
|
an idea to improve |
need to make sure we implement this https://ethresear.ch/t/formally-verified-optimised-epoch-processing/17359/2 looks like we implemented it https://github.com/sigp/lighthouse/blob/d36ebba1eaf4e337fb0038691f2f74ff953b12c7/consensus/state_processing/src/per_epoch_processing/single_pass.rs#L174 |
closing since we've done a lot of work to reduce epoch transition time |
Epoch transition avg time on mainnet up from 700ms, 900ms
Also noting that there's significant variability on the times looking as histogram. The variability is previous to capella tho, would be cool to ensure it's a temporary issue (high GC) or that some states do indeed take more time to process
The text was updated successfully, but these errors were encountered: