From f72d35a78d4436c662cfafbceb829144cd4011fd Mon Sep 17 00:00:00 2001 From: Stefano Brivio Date: Wed, 24 Jul 2024 22:40:32 +0200 Subject: test: iperf3 3.16 introduces multiple threads, drop our own implementation of that Starting from iperf3 version 3.16, -P / --parallel spawns multiple clients as separate threads, instead of multiple streams serviced by the same thread. So we can drop our lib/test implementation to spawn several iperf3 client and server processes and finally simplify things quite a bit. Adjust number of threads and UDP sending bandwidth to values that seem to be more or less matching previous throughput tests on my setup. Signed-off-by: Stefano Brivio Reviewed-by: David Gibson Tested-by: David Gibson --- test/lib/perf_report | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/lib/perf_report') diff --git a/test/lib/perf_report b/test/lib/perf_report index 67f9f4e..4d79fa2 100755 --- a/test/lib/perf_report +++ b/test/lib/perf_report @@ -18,7 +18,7 @@ PERF_LINK_COUNT=0 PERF_JS="${LOGDIR}/web/perf.js" PERF_TEMPLATE_HTML="document.write('"' -Throughput in Gbps, latency in µs. Threads are iperf3 processes, passt and pasta are currently single-threaded.
+Throughput in Gbps, latency in µs. Threads are iperf3 threads, passt and pasta are currently single-threaded.
Click on numbers to show test execution. Measured at head, commit __commit__.