Skip to content
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

Merged
merged 6 commits into from
Apr 23, 2024

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Apr 18, 2024

This should be configured on the runtime level and not somewhere inside the pallet.

This should be configured on the runtime level and not somewhere inside
the pallet.
@bkchr bkchr added the T8-polkadot This PR/Issue is related to/affects the Polkadot network. label Apr 18, 2024
@@ -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);
Copy link
Contributor

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?

polkadot/runtime/parachains/src/coretime/mod.rs Outdated Show resolved Hide resolved
polkadot/runtime/rococo/src/lib.rs Outdated Show resolved Hide resolved
polkadot/runtime/rococo/src/lib.rs Outdated Show resolved Hide resolved
polkadot/runtime/westend/src/lib.rs Outdated Show resolved Hide resolved
polkadot/runtime/westend/src/lib.rs Outdated Show resolved Hide resolved
@bkchr bkchr requested review from athei, andresilva and a team as code owners April 18, 2024 21:02
@bkchr bkchr force-pushed the bkchr-expose-max-transact-weight branch from f72e3c0 to c50659a Compare April 18, 2024 21:04
@Polkadot-Forum
Copy link

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

@bkchr bkchr enabled auto-merge April 23, 2024 09:28
@bkchr bkchr added this pull request to the merge queue Apr 23, 2024
Merged via the queue into master with commit ac4f421 Apr 23, 2024
135 of 138 checks passed
@bkchr bkchr deleted the bkchr-expose-max-transact-weight branch April 23, 2024 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T8-polkadot This PR/Issue is related to/affects the Polkadot network.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants