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

Enabling 1k validators & 200 cores on polkadot #5867

Open
1 of 21 tasks
alexggh opened this issue Sep 30, 2024 · 2 comments
Open
1 of 21 tasks

Enabling 1k validators & 200 cores on polkadot #5867

alexggh opened this issue Sep 30, 2024 · 2 comments

Comments

@alexggh
Copy link
Contributor

alexggh commented Sep 30, 2024

The majority of the optimisations we deem necessary for achieving 1k validators and 200 cores polkadot from this board had been finished or in progress to be finished.

This ticket's purpose is to track all the dependencies that need to happen to gradually reach 1k validators on Kusama and Polkadot. That will allow both networks to have a maximum total cores of 200, we don't have any control over the usage of those cores, but hopefully that ramps up as well.

Checklist to target

Note all the steps are mandatory and are meant to be performed one after the other, if at any step we discovered anything not going according to expectations or if new data is discovered we are meant to pause and reassess the plan.

Kusama

Polkadot

All steps have as a pre-requisite that the same step have already been performed on kusama.

  • Increase the number of parachain validators from 400 to 500, monitor load/stability. OpenGov Referenda
  • approval-voting-parallel is enabled on polkadot, monitor load/stability.
  • PVF prioritization PRs Add PVF execution priority #4837, is enabled on polkadot.
  • Parachain inherent fixes are deployed on polkadot.
  • Validators upgrade their specs inline with: https://polkadot.subsquare.io/referenda/1051?tab=timeline.
  • Bump number of PVF execution workers from 2 to 4
  • Increase the number of parachain validators from 500 to 600, monitor load/stability.
  • Increase the number of parachain validators from 600 to 700, monitor load/stability.
  • Increase the number of parachain validators from 700 to 800, monitor load/stability.
  • Increase the number of parachain validators from 800 to 900, monitor load/stability.
  • Increase the number of parachain validators from 900 to 1000, monitor load/stability.

Honorable mentions

Migrating from the CPU intensive libp2p to litep2p, paritytech/litep2p#140

@burdges

This comment was marked as duplicate.

@alexggh
Copy link
Contributor Author

alexggh commented Sep 30, 2024

We should reserve half the cores for gluttons for the near future.

We already have this one: #5593, but I don't think should be made as a dependency of increasing the number of validators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants