You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
It would be good to have a metric how long the creation of a block actually takes, in order to debug long block times seen on Rococo in the event of lots of disputes. Also seeing time differences in block creation versus block validation/execution are likely to help in pin pointing issues.
In the end parachain inherents get passed to babe where the actual block production is going to happen.
For example on block production the list of recent disputes is accumulating once dispute spam is starting over time until a full session window has passed. So we would expect the block creation time to increase over the course of that session window, while the block validation time should mostly be a function of the current dispute rate and should not increase over time (if dispute rate is constant).
The text was updated successfully, but these errors were encountered:
It would be good to have a metric how long the creation of a block actually takes, in order to debug long block times seen on Rococo in the event of lots of disputes. Also seeing time differences in block creation versus block validation/execution are likely to help in pin pointing issues.
In the end parachain inherents get passed to babe where the actual block production is going to happen.
@emostov @Lldenaurois @drahnr
For example on block production the list of recent disputes is accumulating once dispute spam is starting over time until a full session window has passed. So we would expect the block creation time to increase over the course of that session window, while the block validation time should mostly be a function of the current dispute rate and should not increase over time (if dispute rate is constant).
The text was updated successfully, but these errors were encountered: