-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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.
LGTM, though the weight reductions are somewhat surprising to me (might be that I missed some changes to benchmarks?).
needs a companion, no? |
@apopiak i will make a larger companion with multiple weight files. Since this doesnt break the API, we should be good to go. As for reduction in weights, its hard to say exactly what caused it, but I can say that I am getting consistent results with the current substrate, and i see no reason to think the new weights are not accurate. |
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.
PR is good to me
.max(T::WeightInfo::approve_as_multi_approve(s)) | ||
.max(T::WeightInfo::approve_as_multi_complete(s)) | ||
.saturating_add(*max_weight) | ||
}] |
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.
here the call is still decoded in some situation (like if it gets complete), thus decoding the code is still O(call_len)
but anyway it should be small (like we don't hash it here). And it hasn't been introduced by this PR.
Ain't the weight of |
@kianenigma but results are consistent on the benchmark machine. I have nothing else to really go off of. |
Co-authored-by: Alexander Popiak <alexander.popiak@parity.io>
bot merge |
Trying merge. |
* as multi threshold 1 * add `as_multi_approve_store` benchmark * finish update * final weights * integrate into runtime * whitelist accounts * whitelisted caller weights * clean up comments * Get up to date `call_len` * better implementation * fix spacing * spacing * Update frame/multisig/src/benchmarking.rs Co-authored-by: Alexander Popiak <alexander.popiak@parity.io> Co-authored-by: Alexander Popiak <alexander.popiak@parity.io>
This introduces the automated benchmarking freamwork to the Multisig Pallet.
All extrinsic weights are now represented by a configurable
WeightInfo
.as_multi_threshold_1
Before
After
as_multi_create
Before
After
as_multi_create_store
Before
Missing
contains_key
read, so the new weight is correctAfter
as_multi_approve
Before
Overweight by 1 read?
confirmed by https://www.shawntabrizi.com/substrate-graph-benchmarks/db-stats.html?p=multisig&e=as_multi_approve
After
cancel_as_multi
Old weight is overweight by 1 read and write due to not whitelisting