-
Notifications
You must be signed in to change notification settings - Fork 743
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
[xcm] Use Weight::MAX
for reserve_asset_deposited
, receive_teleported_asset
benchmarks
#1726
Conversation
…orted_asset` benchmarks
bot help |
Here's a link to docs |
bot bench cumulus-assets --runtime asset-hub-polkadot --subcommand xcm --pallet pallet_xcm_benchmarks::fungible |
"$PIPELINE_SCRIPTS_DIR/commands/bench/bench.sh" --subcommand=xcm --runtime=asset-hub-polkadot --runtime_dir=assets --target_dir=cumulus --pallet=pallet_xcm_benchmarks::fungible was queued. Comment |
@bkontur Command
|
bot bench cumulus-assets --runtime asset-hub-polkadot --subcommand xcm --pallet pallet_xcm_benchmarks::fungible |
@mordamax https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3825853 was started for your command Comment |
…set-hub-polkadot --runtime_dir=assets --target_dir=cumulus --pallet=pallet_xcm_benchmarks::fungible
@mordamax Command |
bot bench cumulus-assets --runtime asset-hub-kusama --subcommand xcm --pallet pallet_xcm_benchmarks::fungible |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828304 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828305 was started for your command Comment |
bot bench cumulus-bridge-hubs --runtime bridge-hub-polkadot --subcommand xcm --pallet pallet_xcm_benchmarks::fungible |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828306 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828307 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828308 was started for your command Comment |
bot bench polkadot-pallet --runtime polkadot --subcommand xcm --pallet pallet_xcm_benchmarks::fungible |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828310 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828319 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828322 was started for your command Comment |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/3828323 was started for your command Comment |
…stend --target_dir=polkadot --pallet=pallet_xcm_benchmarks::fungible
@bkontur Command |
@bkontur Command |
@bkontur Command |
IIRC this was there because the XCM pallet did not have proper benchmarked weights, so once we do, then we can indeed remove it. |
* master: (33 commits) ci: set CI_IMAGE back to (now updated) .ci-unified (#1854) ci: bump ci image to rust 1.73.0 (#1830) Refactor Identity to benchmark v2 (#1838) PVF worker: bump landlock, update ABI docs (#1850) Xcm emulator nits (#1649) Fixes path issue in derive-impl (#1823) upgrade to macro_magic 0.4.3 (#1832) Use safe math when pruning statuses (#1835) remote-ext: fix state download stall on slow connections and reduce memory usage (#1295) Update testnet bootnode dns name (#1712) [FRAME] Warn on unchecked weight witness (#1818) [xcm] Use `Weight::MAX` for `reserve_asset_deposited`, `receive_teleported_asset` benchmarks (#1726) Update bridges subtree (#1803) Check for parent of first ready block being on chain (#1812) Make CheckNonce refuse transactions signed by accounts with no providers (#1578) Fix Asset Hub collator crashing when starting from genesis (#1788) Mixnet integration (#1346) [xcm-emulator] Decouple the `AccountId` type from `AccountId32` (#1458) Treasury spends various asset kinds (#1333) chore: bump zombienter version (#1806) ...
…yLocation` and `SystemParachains` in the same way (#2023) This PR addresses several issues: - simplify referencing `RelayTreasuryLocation` without needing additional `RelayTreasury` struct - fix for referencing `SystemParachains` from parachain with `parents: 1` instead of `parents: 0` - removed hard-coded constants and fix tests for `asset-hub-rococo` which was merged to master after #1726 --------- Co-authored-by: command-bot <>
…yLocation` and `SystemParachains` in the same way (#2023) This PR addresses several issues: - simplify referencing `RelayTreasuryLocation` without needing additional `RelayTreasury` struct - fix for referencing `SystemParachains` from parachain with `parents: 1` instead of `parents: 0` - removed hard-coded constants and fix tests for `asset-hub-rococo` which was merged to master after #1726 --------- Co-authored-by: command-bot <>
…yLocation` and `SystemParachains` in the same way (#2023) This PR addresses several issues: - simplify referencing `RelayTreasuryLocation` without needing additional `RelayTreasury` struct - fix for referencing `SystemParachains` from parachain with `parents: 1` instead of `parents: 0` - removed hard-coded constants and fix tests for `asset-hub-rococo` which was merged to master after #1726 --------- Co-authored-by: command-bot <>
…::new to avoid expects (#1726)
Description
Summary
Previously, the
pallet_xcm::do_reserve_transfer_assets
andpallet_xcm::do_teleport_assets
functions relied on weight estimation for remote chain execution, which was based on guesswork derived from the local chain. This approach led to complications for runtimes that did not provide or support specific XCM configurations forIsReserve
orIsTeleporter
. Consequently, such runtimes had to resort to implementing hard-coded weights for XCM instructions likereserve_asset_deposited
orreceive_teleported_asset
to support extrinsics such aspallet_xcm::reserve_transfer_assets
andpallet_xcm::teleport_assets
, which depended on remote weight estimation.The issue of remote weight estimation was addressed and resolved by Pull Request #1645, which removed the need for remote weight estimation.
Solution
As a continuation of this improvement, the current PR proposes further cleanup by removing unnecessary hard-coded values and rectifying benchmark results with
Weight::MAX
that previously usedT::BlockWeights::get().max_block
as an override for unsupported XCM instructions likeReserveAssetDeposited
andReceiveTeleportedAsset
.Questions
Hardcoded till the XCM pallet is fixed
fordeposit_asset
? E.g. for AssetHubKusama here// Kusama doesn't support ReserveAssetDeposited, so this benchmark has a default weight
still relevant? Shouldnt be removed/changed?TODO
bench bot
regenerate xcm weights for all runtimespolkadot-fellow/runtimes
PRReferences
Fixes #1132
Closes #1132
Old polkadot repo PR