Provide 500ms for speculative blocks #524
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.
Since AntelopeIO/leap#1481 speculative blocks honor block deadlines so that "Start speculative blocks every block interval but not more often". However, since 50ms threshold was use it could set a deadline that would be hit before another block came causing a needless restart of a transaction and restart of a block.
For example:
Instead give a speculative block a full block interval (500ms) before considering it exhausted.