Run subsystem-benchmark without network latency (#4068)

Implements the idea from
https://github.com/paritytech/polkadot-sdk/pull/3899
- Removed latencies
- Number of runs reduced from 50 to 5, according to local runs it's
quite enough
- Network message is always sent in a spawned task, even if latency is
zero. Without it, CPU time sometimes spikes.
- Removed the `testnet` profile because we probably don't need that
debug additions.

After the local tests I can't say that it brings a significant
improvement in the stability of the results. However, I belive it is
worth trying and looking at the results over time.
This commit is contained in:
Andrei Eres
2024-04-11 18:54:59 +02:00
committed by GitHub
parent 6ebf491b50
commit 25f038aa8e
3 changed files with 8 additions and 4 deletions
+2 -2
View File
@@ -524,7 +524,7 @@ subsystem-benchmark-availability-recovery:
- .common-refs
- .run-immediately
script:
- cargo bench --profile=testnet -p polkadot-availability-recovery --bench availability-recovery-regression-bench --features subsystem-benchmarks
- cargo bench -p polkadot-availability-recovery --bench availability-recovery-regression-bench --features subsystem-benchmarks
tags:
- benchmark
allow_failure: true
@@ -542,7 +542,7 @@ subsystem-benchmark-availability-distribution:
- .common-refs
- .run-immediately
script:
- cargo bench --profile=testnet -p polkadot-availability-distribution --bench availability-distribution-regression-bench --features subsystem-benchmarks
- cargo bench -p polkadot-availability-distribution --bench availability-distribution-regression-bench --features subsystem-benchmarks
tags:
- benchmark
allow_failure: true