aboutgitcodebugslistschat
path: root/netlink.c
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2023-11-06 18:08:28 +1100
committerStefano Brivio <sbrivio@redhat.com>2023-11-07 09:56:10 +0100
commite516809a74ffd495481a7adf6b565181861a41f9 (patch)
tree1b99cba3173477677b3b0e6ac203db673fca0cd2 /netlink.c
parentf9ff6678d4bbf5d9c80c1c6f784c3955468c09d6 (diff)
downloadpasst-e516809a74ffd495481a7adf6b565181861a41f9.tar
passt-e516809a74ffd495481a7adf6b565181861a41f9.tar.gz
passt-e516809a74ffd495481a7adf6b565181861a41f9.tar.bz2
passt-e516809a74ffd495481a7adf6b565181861a41f9.tar.lz
passt-e516809a74ffd495481a7adf6b565181861a41f9.tar.xz
passt-e516809a74ffd495481a7adf6b565181861a41f9.tar.zst
passt-e516809a74ffd495481a7adf6b565181861a41f9.zip
test/perf: Start iperf3 server less often
Currently we start both the iperf3 server(s) and client(s) afresh each time we want to make a bandwidth measurement. That's not really necessary as usually a whole batch of bandwidth measurements can use the same server. Split up the iperf3 directive into 3 directives: iperf3s to start the server, iperf3 to make a measurement and iperf3k to kill the server, so that we can start the server less often. This - and more importantly, the reduced number of waits for the server to be ready - reduces runtime of the performance tests on my laptop by about 4m (out of ~28minutes). For now we still restart the server between IPv4 and IPv6 tests. That's because in some cases the latency measurements we make in between use the same ports. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'netlink.c')
0 files changed, 0 insertions, 0 deletions