Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Understand the hardware requirements for simple nightshade block producers #4561

Closed
bowenwang1996 opened this issue Jul 23, 2021 · 1 comment · Fixed by #4785
Closed

Understand the hardware requirements for simple nightshade block producers #4561

bowenwang1996 opened this issue Jul 23, 2021 · 1 comment · Fixed by #4785
Assignees
Labels
Node Node team P-high Priority: High T-node Team: issues relevant to the node experience team

Comments

@bowenwang1996
Copy link
Collaborator

bowenwang1996 commented Jul 23, 2021

When we transition from one shard to eight shards in simple nightshade, block producers need to track all shards. As a result, they may need to have better hardware (more cpus more example) than what is currently specified in the docs. After #3825 is done, we should run some experiments to understand what changes to hardware are needed for block producers. We could then potentially batch this change in hardware requirements with #4461 to update the fees.

@bowenwang1996 bowenwang1996 added the T-node Team: issues relevant to the node experience team label Jul 23, 2021
@bowenwang1996 bowenwang1996 added the P-high Priority: High label Aug 17, 2021
@bowenwang1996
Copy link
Collaborator Author

To be more specific, we need:

  • A cluster with 100 nodes running and loadtest it with transactions. For this part we can take/modify the existing mocknet scripts
  • We also need to change the genesis configuration to make sure that every validator tracks all 8 shards. This can be done by modifying num_block_producer_seats_per_shard.

cc @nikurt

@nikurt nikurt linked a pull request Sep 16, 2021 that will close this issue
@gmilescu gmilescu added the Node Node team label Oct 19, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Node Node team P-high Priority: High T-node Team: issues relevant to the node experience team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants