-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Conversation
this was run off d17f062 |
Weight::from_ref_time(105_000 as u64) | ||
} | ||
/// The range of component `i` is `[0, 1000000]`. | ||
fn subtraction(_i: u32, ) -> Weight { | ||
Weight::from_ref_time(125_000 as u64) | ||
Weight::from_ref_time(112_000 as u64) |
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.
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.
I think the increased precision only applied to the linear component, or @koute ?
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.
that makes sense
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.
Correct, the increased precision is only for the component weights, as that's where it can make a difference.
Weight::from_ref_time(5_800_910_000 as u64) | ||
// Standard Error: 141_466 | ||
.saturating_add(Weight::from_ref_time(5_793_269 as u64).saturating_mul(v as u64)) | ||
// Standard Error: 14_463_035 | ||
.saturating_add(Weight::from_ref_time(1_592_527_344 as u64).saturating_mul(d as u64)) | ||
} | ||
/// The range of component `v` is `[1000, 2000]`. | ||
/// The range of component `t` is `[500, 1000]`. | ||
/// The range of component `d` is `[5, 16]`. | ||
fn phragmms(v: u32, _t: u32, d: u32, ) -> Weight { | ||
Weight::from_ref_time(0 as u64) | ||
// Standard Error: 79_000 | ||
.saturating_add(Weight::from_ref_time(14_480_000 as u64).saturating_mul(v as u64)) | ||
// Standard Error: 6_844_000 | ||
.saturating_add(Weight::from_ref_time(2_525_332_000 as u64).saturating_mul(d as u64)) | ||
Weight::from_ref_time(4_696_655_000 as u64) | ||
// Standard Error: 150_968 | ||
.saturating_add(Weight::from_ref_time(5_769_927 as u64).saturating_mul(v as u64)) | ||
// Standard Error: 15_434_495 | ||
.saturating_add(Weight::from_ref_time(1_820_652_967 as u64).saturating_mul(d as u64)) |
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.
big changes here
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.
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.
It does look like this weight was affected by the zero base weight issue that my PR fixed; looks correct to me. As @ggwpez pointed out this actually lowered the weight final weight since the negative base weight isn't rounded up to zero anymore (so we were overestimating how costly this extrinsic was when the components are not zero)
/cmd queue -v RUST_LOG=debug -c bench-bot $ runtime kusama-dev pallet_balances |
@shawntabrizi https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/1864571 was started for your command Comment |
@shawntabrizi Command |
Interesting. There are some big increases, but also a lot of decreases. SWC-compare link link and PDF for posterity. |
westend wasn't ready when i opened the PR - it is now, i'll add the files. |
.saturating_add(T::DbWeight::get().reads(3 as u64)) | ||
.saturating_add(T::DbWeight::get().reads((1 as u64).saturating_mul(p as u64))) | ||
.saturating_add(T::DbWeight::get().writes(2 as u64)) | ||
.saturating_add(T::DbWeight::get().writes(3 as u64)) |
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.
changes
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.
So the weights were outdated somehow
doesn't compile, however |
Looks like an error in the template, should be easy to resolve, will look into it |
Could also just be missing deps in |
Regarding the merge conflicts: its since we renamed |
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
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.
The large changes are most likely from the recent weight calculation changes. We are investigating them in Substrate.
Should be more precise now 😄
@@ -1,28 +1,27 @@ | |||
// This file is part of Substrate. | |||
// Copyright 2017-2022 Parity Technologies (UK) Ltd. |
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.
I added the correct file header manually. All future MRs should have them automatically #5984
new weights as requested by @shawntabrizi