WIP: add Scenario1 definition #31
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
leobago
reviewed
Mar 28, 2023
| runs = range(1) | ||
|
|
||
| # Number of validators | ||
| numberNodes = [8000] |
There was a problem hiding this comment.
Our crawler Armiarma currently shown about 11K beacon nodes in the network, I would suggest using that.
|
|
||
| # distribute rows/columns evenly between validators (True) | ||
| # or generate it using local randomness (False) | ||
| evenLineDistribution = False |
| blockSizes = [512] | ||
|
|
||
| # Per-topic mesh neighborhood size | ||
| netDegrees = [6] |
There was a problem hiding this comment.
I think the current value is 8. Forgot where I saw it though.
| chis = [2] | ||
|
|
||
| # ratio of class1 nodes (see below for parameters per class) | ||
| class1ratios = [0.8] |
There was a problem hiding this comment.
More like 0.9 based on Armiarma.
|
|
||
| # number of validators per beacon node | ||
| validatorsPerNode1 = [1] | ||
| validatorsPerNode2 = [100] |
There was a problem hiding this comment.
I think 500 is more realistic, based on Lido's report. Also, is the value recommended by Dankrad.
| # Set uplink bandwidth. In segments (~560 bytes) per timestep (50ms?) | ||
| # 1 Mbps ~= 1e6 / 20 / 8 / 560 ~= 11 | ||
| bwUplinksProd = [11000] | ||
| bwUplinks1 = [110] |
There was a problem hiding this comment.
I would love to have these three in Mbps.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is currently a placeholder for Scenario 1, while we decide the final numbers