-
Notifications
You must be signed in to change notification settings - Fork 809
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
Properly benchmark set_validation_data
#6772
Labels
D1-medium
Can be fixed by a coder with good Rust knowledge but little knowledge of the codebase.
I5-enhancement
An additional feature request.
Comments
Let me take a crack at it @skunert |
Thank you! Feel free to take a stab at it! |
Hey @Doordashcon , do you still plan to take a look into this? |
yes @skunert |
Draft
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 25, 2025
…n the pre dispatch is zero. (#7327) Related #6772 For an extrinsic, in the post dispatch info, the actual weight is only used to reclaim unused weight. If the actual weight is more than the pre dispatch weight, then the extrinsic is using the minimum, e.g., the weight used registered in pre dispatch. In parachain-system pallet one call is `set_validation_data`. This call is returning an actual weight, but the pre-dispatch weight is 0. This PR fix the disregard of actual weight of `set_validation_data` by registering it manually.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
D1-medium
Can be fixed by a coder with good Rust knowledge but little knowledge of the codebase.
I5-enhancement
An additional feature request.
On parachains, we have the
set_validation_data
inherent that needs to be present in every block.It is returning some weight at the moment, but there is no proper benchmark and I assume that the Weight return is not accurate.
Location:
polkadot-sdk/cumulus/pallets/parachain-system/src/lib.rs
Lines 568 to 571 in f4a196a
The text was updated successfully, but these errors were encountered: