You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Block-packing with reserve/commit scheme is inefficient
Transactions may reserve much more than they actually use
This can block other transactions from executing
Proposed Solution
Move from a reserve/commit cost-tracking scheme to execute/commit
Do not reserve CUs in cost-tracker before execution. Just check we are not much higher than block-limits
Before recording, check which transactions can fit into the block and commit their costs.
IF recording fails, the committed costs need to be rolled back (otherwise do nothing here)
This can lead to us executing transactions that we cannot actually record, BUT it will only occur when we are full/near full.
This trade-off is favorable, in my view, because we are more likely to fill the block and we don't necessarily care if we waste a few cycles executing when our block is getting filled. If the block is full, then those wasted cycles are not blocking other transactions.
The text was updated successfully, but these errors were encountered:
Problem
Proposed Solution
This can lead to us executing transactions that we cannot actually record, BUT it will only occur when we are full/near full.
This trade-off is favorable, in my view, because we are more likely to fill the block and we don't necessarily care if we waste a few cycles executing when our block is getting filled. If the block is full, then those wasted cycles are not blocking other transactions.
The text was updated successfully, but these errors were encountered: