feat: drop jito bundle size and improve packing #2940
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Before this change, the instruction packing algorithm was assuming every transaction had the Jito tip, this was leading to suboptimal packing (in reality only the first transaction of each bundle has the jito tip).
Rather than giving knowledge of
jitoBundleSizetoaddInstruction, I decided to hardcodeJITO_BUNDLE_SIZEto the maximum of 5 everywhere (why would anyone want to send bundles smaller than the maximum?). NowaddInstructioncan know which transactions may have a Jito tip transfer.Rationale
This allows the scheduler to land 2 updates per transaction like before the last Merkle Proof size increase.
How has this been tested?
I run the scheduler locally with the prod config.