🐞 [Bug]: Unexpectedly high weights/fees for `pallet_xcm`

[ozgunozerk]

templates

• [X] Generic Runtime Template
• [X] Evm Template

What happened?

Discovered by @DrW3RK (thank you!): In both generic and evm templates, under pallet-xcm weights, we have unexpectedly high weights assigned to:

• teleport_assets
• reserve_transfer_assets
• transfer_assets
• execute
• execute_blob

AFAIK, these weights are generated on a specific machine with benchmarking commands.

We should find the reason for why the benchmarking generated these absurd weights. Or, if they are expected to be that high, we should maybe explain that better in our docs or inline docs.

Expected behavior

No response

Contribution Guidelines

• [X] I agree to follow this project's Contribution Guidelines

[ozgunozerk]

@KitHat do you have any idea on what's going on? Feel free to assign yourself if you see fit

[franciscoaguirre]

This impossible weights are assigned when there is no reservable or teleportable assets configured in the benchmarks, see: https://github.com/paritytech/polkadot-sdk/blob/86bb5cb5068463f006fda3a4ac4236686c989b86/polkadot/xcm/pallet-xcm/src/benchmarking.rs#L153 for example