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.
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
subsystem-bench: add regression tests for availability read and write #3311
subsystem-bench: add regression tests for availability read and write #3311
Changes from 16 commits
c01894b
f71c502
733f0eb
fdc1392
815c023
0a65126
42963a9
98224fd
d98b899
5175897
a721bca
b27edaa
9136955
18a0c7e
d72a035
d161de1
ab2e179
1e59be1
b54b85d
0e4432a
3b6a3e9
2fec1c1
2657432
c037885
d46e9fa
708e002
d1b3631
282745a
f6df907
f0aea37
ff7dac3
e1e6f2d
68ec964
184eee1
f03f4a7
4abf5d8
9df54ec
3acfe18
3868962
e4f3c87
f55ae88
222f791
ddf4408
4f40d1f
0e1b59e
31a5090
732b4ba
c0e6f31
02d63b8
341c8b7
a03fd98
77f3da5
36b3f6c
ff91819
46ec768
07b4662
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this value correct as per validator specs (500 Mbit/s (= 62.5 MB/s)) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexggh what do you think? I just copied it from your yaml.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is different than approval voting setup. It would be better to have the correct value set in default impl of config, and include a comment when we override it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why 75 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copied from
availability_write.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This value should be set to the number of block validators are expected to check per relay chain block. This depends on approval voting parameters. We should also factor in async backing, that is we'd expect to have 1 included candidate at every block.
We can calibrate these in the followup PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just sorted to unify the order in all test cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unused parameter.