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

Incorporate pallet_migrations for future migrations #593

Closed
sam0x17 opened this issue Jun 27, 2024 · 1 comment
Closed

Incorporate pallet_migrations for future migrations #593

sam0x17 opened this issue Jun 27, 2024 · 1 comment

Comments

@sam0x17
Copy link
Contributor

sam0x17 commented Jun 27, 2024

Context

The recent runtime upgrade from 145 to 146 took 7-8 blocks at 240s per block until the upgrade finished on all nodes.
This upgrade triggered a large chain migration, causing blocks to be finalized only after all the authority nodes were finished with the migration, slowing the chain significantly.

Solution

We should incorporate better handling of chain migrations. Parity developed a solution for this in FRAME1. This pallet handles large migrations much better, so we should incorporate it into our chain and utilize it in future migrations.

Footnotes

  1. See related PR: https://github.com/paritytech/polkadot-sdk/pull/1781

@sam0x17
Copy link
Contributor Author

sam0x17 commented Jul 2, 2024

closing in favor of #596

@sam0x17 sam0x17 closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant