-
Notifications
You must be signed in to change notification settings - Fork 680
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
☂️ Small benchmarking issues #391
Comments
@ggwpez the related issue is done. Can I take this? |
Yea sure @kziemianek! Someone else also wanted to work on it, but I did not hear back from them. |
@ggwpez I'm working on this. |
@ggwpez I have a draft PR for this here: paritytech/substrate#11893 But I need clarity on results to save to JSON, and also where/how the |
Why should the default value for |
I see, now I understand that the default key for System::BlockWeight. Thank you for clarifying that up for me. |
Some follow-ups from paritytech/substrate#11091:
benchmark-overhead
command polkadot#5137benchmark-overhead
command polkadot#5137overhead
sub-command:--header
flag analogous to thepallet
sub-command to support any file-header Add--header
tobenchmark overhead + storage
substrate#12204Wasm
substrate#11170 made wasm default.--block-weight-key
flag with default26aa394eea5630e07c48ae0c9558cef734abf5cb34d6244378cddbf18e849d96
from
andto
can be negative to go into the past from the best block.for_keys_with_prefix
needs to useadd_read_key
This is a good issue for external contributors.
Should be done after paritytech/substrate#11140
The text was updated successfully, but these errors were encountered: