Change Fixed to WeightInfoBounds for Polkadot#7077
Change Fixed to WeightInfoBounds for Polkadot#7077paritytech-processbot[bot] merged 67 commits intomasterfrom
Conversation
|
bot bench $ xcm polkadot pallet_xcm_benchmarks::fungible |
0193228 to
e164da6
Compare
|
bot bench $ xcm polkadot pallet_xcm_benchmarks::fungible |
|
bot clean |
|
bot bench $ xcm polkadot pallet_xcm_benchmarks::generic |
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
runtime/polkadot/src/weights/xcm/pallet_xcm_benchmarks_fungible.rs
Outdated
Show resolved
Hide resolved
|
bot bench $ xcm kusama pallet_xcm_benchmarks::generic |
Signed-off-by: Oliver Tale-Yazdi <[email protected]>
|
Updated manually. bot cancel |
|
bot rebase |
|
bot merge |
|
bot help |
|
bot rebase |
|
bot fmt |
|
bot clean |
|
bot rebase |
…weight-info-bound
|
Rebased |
|
bot merge |
|
Waiting for commit status. |
|
hmm, I wonder, how could this pass without companion to cumulus? probably job does not check benchmarks, |
Addresses #6785
The Polkadot XCM Weigher was previously using a fixed weight for each XCM instruction.
This PR changes that to actual benchmarked weights.
We were using
1_000_000_000of weight in ref_time and0in proof_size.The new weights are all way less than that in ref_time which means developers right now might be overpaying and could pay way less for weight for their messages.