Don't fast-track large block submissions #451
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.
📝 Summary
Large block submissions (i.e. with transactions from L2 rollups) are severely impacting block submission and simulation latency.
This change will not fast-track payloads above a certain size (230kb by default).
⛱ Motivation and Context
This chart shows how all slow fast-tracked submissions are due to large payloads:
Even in high-priority, the submissions will still get accepted, but without blocking fast-tracked ones from succeeding quickly.
⚡ Impact
After deploying this change, the average fast-track submission time is <200ms:
Last 48h:
Last 3h:
✅ I have run these commands
make lint
make test-race
go mod tidy
CONTRIBUTING.md