Add RPC resource limit estimation opt-out#290
Open
catmcgee wants to merge 1 commit into
Open
Conversation
🦋 Changeset detectedLatest commit: f534476 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
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.
Adds
resourceLimitEstimation: "estimate" | "none"to the RPC planner/executor path.By default, behavior is unchanged: the planner reserves provisional resource-limit instructions and the executor estimates/sets missing limits before sending
When set to
none:rpcTransactionPlannerdoes not add provisional resource-limit instructionsrpcTransactionPlanExecutordoes not simulate to estimate or inject missing limitssolanaRpcpasses the same setting to both planner and executorThis is useful for transactions that are close to the message size limit, where adding a compute-budget instruction can make an otherwise valid transaction too large