aboutgitcodebugslistschat
path: root/test/perf/pasta_tcp
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2023-11-06 18:08:27 +1100
committerStefano Brivio <sbrivio@redhat.com>2023-11-07 09:56:06 +0100
commitf9ff6678d4bbf5d9c80c1c6f784c3955468c09d6 (patch)
tree2801702f83f832322052c98c5ae68f94d2cdf106 /test/perf/pasta_tcp
parent8a41a8b20f0f5a6c497bccbb41198277f9a865f8 (diff)
downloadpasst-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar.gz
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar.bz2
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar.lz
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar.xz
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.tar.zst
passt-f9ff6678d4bbf5d9c80c1c6f784c3955468c09d6.zip
test/perf: Get iperf3 stats from client side
iperf3 generates statistics about its run on both the client and server sides. They don't have exactly the same information, but both have the pieces we need (AFAICT the server communicates some nformation to the client over the control socket, so the most important information is in the client side output, even if measured by the server). Currently we use the server side information for our measurements. Using the client side information has several advantages though: * We can directly wait for the client to complete and we know we'll have the output we want. We don't need to sleep to give the server time to write out the results. * That in turn means we can wrap up as soon as the client is done, we don't need to wait overlong to make sure everything is finished. * The slightly different organisation of the data in the client output means that we always want the same json value, rather than requiring slightly different onces for UDP and TCP. The fact that we avoid some extra delays speeds up the overal run of the perf tests by around 7 minutes (out of around 35 minutes) on my laptop. The fact that we no longer unconditionally kill client and server after a certain time means that the client could run indefinitely if the server doesn't respond. We mitigate that by setting 1s connect timeout on the client. This isn't foolproof - if we get an initial response, but then lose connectivity this could still run indefinitely, however it does cover by far the most likely failure cases. --snd-timeout would provide more robustness, but I've hit odd failures when trying to use it. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/perf/pasta_tcp')
0 files changed, 0 insertions, 0 deletions