docs: clarify tx-wide default max units explainer
This commit is contained in:
parent
e8bdc27080
commit
9bca909f63
|
@ -113,10 +113,11 @@ Budget](#compute-budget).
|
||||||
|
|
||||||
With a transaction-wide compute budget the `max_units` cap is applied to the
|
With a transaction-wide compute budget the `max_units` cap is applied to the
|
||||||
entire transaction rather than to each instruction within the transaction. The
|
entire transaction rather than to each instruction within the transaction. The
|
||||||
default number of maximum units will calculated per instruction which means the
|
transaction-wide default maximum number of units will be calculated as the product
|
||||||
sum of the compute units used by each instruction in the transaction must not
|
of the instruction count and the existing per-instruction maximum units. This means
|
||||||
exceed that value. The default number of maximum units allowed matches existing
|
that the sum of the compute units used by each instruction in the transaction must
|
||||||
values to avoid breaking existing client behavior.
|
not exceed that value. This default maximum value attempts to retain existing behavior
|
||||||
|
to avoid breaking client logic.
|
||||||
|
|
||||||
### Reduce transaction fees
|
### Reduce transaction fees
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue