-
Couldn't load subscription status.
- Fork 2.7k
Update System Weights #5888
Update System Weights #5888
Conversation
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.
just some suggestions
Co-authored-by: Alexander Popiak <[email protected]>
This reverts commit 95bd276.
This is erroneous. There are instances where you may wish the Scheduler to be able to schedule a lower amount of weight than the block. It's quite reasonable, for instance, that you would only want to give 50% of the block over to (non-mandatory) scheduled tasks and leave the remainder for transactions. |
|
The weight is now updated using So I believe this can get any final reviews and green check-marks. |
|
bot merge |
This PR updates the weights of FRAME System
Pretty straightforward, but we should be extra careful of the functions that use a full block (set_code and set_code_without_checks).
I would like to make sure there is no trivial mistake here that would prevent this extrinsic from entering a block. Does anyone see any issues?
Notable Changes:
kill_prefixto allow the Root user to tell us the number of subkeys under a prefix so that we may weight the function correctly. This parameter is not checked.sudo_unchecked_weightfunction, which ignores the weight of the dispatch call and instead uses any weight defined by the Sudo user. This can be helpful when trying to push a runtime upgrade where you dont have (or want) the scheduler.