feat(bin): disable ETA for execution stage #5839
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We receive a lot of reports from users who are confused about the ETA for
Execution
stage, e.g.:The problem is that our ETA works only on two points (previous and current timestamps), and the progress for
Execution
stage is measured in gas, which is likely not an ideal proxy for real CPU time.For the time being, I think we should disable the ETA reporting for
Execution
stage completely, and leave just the percentage progress which should be enough to get the idea of how long it takes to complete.