-
Notifications
You must be signed in to change notification settings - Fork 732
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
parachains_coretime: Expose MaxXCMTransactWeight
#4189
Conversation
This should be configured on the runtime level and not somewhere inside the pallet.
polkadot/runtime/westend/src/lib.rs
Outdated
@@ -1188,6 +1188,7 @@ impl parachains_scheduler::Config for Runtime { | |||
|
|||
parameter_types! { | |||
pub const BrokerId: u32 = BROKER_ID; | |||
pub MaxXCMTransactWeight: Weight = Weight::from_parts(200_000_000, 20_000); |
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.
Set lease has three reads and a write, independent of the ref time of the actual function on that runtime that already means a ref_time
of 175_000_000
. Is it worth leaving a bit more of a buffer to account for fluctuations in benchmarking on top of this?
Co-authored-by: Branislav Kontur <[email protected]>
f72e3c0
to
c50659a
Compare
This pull request has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/kusama-v1-2-0-coretime-migration-xcm-failure-a-postmortem/7536/1 |
This should be configured on the runtime level and not somewhere inside the pallet.