-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: clarify tx-wide default max units explainer #24955
Conversation
I updated docs in the backports while fixing the merge errors but this looks great too! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nice, this is much clearer, thanks!
exceed that value. The default number of maximum units allowed matches existing | ||
values to avoid breaking existing client behavior. | ||
transaction-wide default maximum number of units will be calculated as the product | ||
of the instruction count and the existing per-instruction maximum units. This means |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also mention that the calculated max is clamped at 1.4M compute units?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Considered referencing the current constant values, but decided I didn't want to be responsible for keeping them up to date
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we say something like "at the time of writing, this caps at 1.4M but it's subject to change" as a cop out? I think it's useful
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no precedent for citing other constant values in this file. Feel free to add them if you feel strongly!
Problem
unclear description of how tx-wide compute budget will calculate the default maximum units
Summary of Changes
attempt to clarify it