mirror of
https://passt.top/passt
synced 2025-05-21 00:35:34 +02:00
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 <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Tested-by: David Gibson <david@gibson.dropbear.id.au>
This commit is contained in:
parent
606e0c7b95
commit
f72d35a78d
6 changed files with 127 additions and 145 deletions
test/lib
|
@ -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 <span style="font-family: monospace;">iperf3</span> processes, <i>passt</i> and <i>pasta</i> are currently single-threaded.<br/>
|
||||
Throughput in Gbps, latency in µs. Threads are <span style="font-family: monospace;">iperf3</span> threads, <i>passt</i> and <i>pasta</i> are currently single-threaded.<br/>
|
||||
Click on numbers to show test execution. Measured at head, commit <span style="font-family: monospace;">__commit__</span>.
|
||||
|
||||
<style type="text/CSS">
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue