On 06/09/2025 1:32, Jakub Kicinski wrote:
On Tue, 2 Sep 2025 16:21:01 -0700 Jakub Kicinski wrote:
On Sun, 31 Aug 2025 11:06:41 +0300 Carolina Jubran wrote:
Because the measured total is the sum of two iperf3 streams that do not
always start or stop at the same time
That's solvable, tho? iperf3 has --json support, it will give you
the b/w readings in the configured intervals (1sec by default).
With the interval based samples at hand you should be able to select
only the period in which b/w is stable ("middle" of the test).
While at it it may make sense to switch to lib/py/load.py wrappers
rather than threading the python locally in the test.
Hi Carolina! I think you replied to me but the reply never reached
the list, I purged it from my inbox before realizing.
:O Sorry about that
I think you said that the direction of the flows is wrong for load.py.
Yes, that’s exactly what I said.
Perhaps adding a reverse= attr which will translate the --reverse in
the client process would do?
However, I’ll also need to extend load.py:
1. Binding support to ensure traffic flows through the specific VLAN
interface.
2. Interval-based measurement for iperf3 --json to analyze only the
stable period.
So my plan is:
1. Send v2 for net to fix the current test with interval-based
measurement.
2. Follow up with a patch to extend load.py with reverse/binding/interval
support and then migrate the test to use it.
Does that sound good to you?
Thanks again for the suggestion :)
