Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fixup to values obtained with production profile instead of testnet
Signed-off-by: Alexandru Gheorghe <[email protected]>
  • Loading branch information
alexggh committed Jul 31, 2024
commit 2e3ddc3e4ab8d7dae8dcea926433f6c16c1713da
11 changes: 7 additions & 4 deletions prdoc/pr_5196.prdoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,15 @@ title: Bring benchmark inline with reference machine used for weights
doc:
- audience: Node Operator
description: |
- BLAKE2-256 reference values were too low(~20) when compared with the machine used for generating
- BLAKE2-256 reference values were too low(~30%) when compared with the machine used for generating
the weights, so it was brought in sync with results on the reference hardware recommended here:
https://wiki.polkadot.network/docs/maintain-guides-how-to-validate-polkadot#reference-hardware
- Validators where the `BLAKE2-256` was barely passing, might received the warning that they are
not compliant anymore, this should not be treated as critical, but they should take the necessary
steps to become compliant in the near/mid-term future.
- SR25519-Verify reference values were too low(~10%) when compared with the machine used for generating
the weights, so it was brought in sync with results on the reference hardware recommended here:
https://wiki.polkadot.network/docs/maintain-guides-how-to-validate-polkadot#reference-hardware
- Validators where the `BLAKE2-256` and `SR25519-Verify` were barely passing, might received the
warning that they are not compliant anymore, this should not be treated as critical, but they
should take the necessary steps to become compliant in the near/mid-term future.
- Note!: The reference hardware requirements have not been increased we just fixed the benchmark which
was wrongly reporting lower spec HW as being compliant.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ mod tests {
assert_eq!(
*SUBSTRATE_REFERENCE_HARDWARE,
Requirements(vec![
Requirement { metric: Metric::Blake2256, minimum: Throughput::from_mibs(968.31) },
Requirement { metric: Metric::Blake2256, minimum: Throughput::from_mibs(1000.00) },
Requirement {
metric: Metric::Sr25519Verify,
minimum: Throughput::from_kibs(560.670000128),
minimum: Throughput::from_kibs(637.619999744),
},
Requirement {
metric: Metric::MemCopy,
Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
[
{
"metric": "Blake2256",
"minimum": 968.31
"minimum": 1000.00
},
{
"metric": "Sr25519Verify",
"minimum": 0.547529297
"minimum": 0.622675781
},
{
"metric": "MemCopy",
Expand Down