iperf3 -O (--omit) to get more than 60 seconds omit time

[tblaszcz]

NOTE: The iperf3 issue tracker is for registering bugs, enhancement requests, or submissions of code. It is not a means for asking questions about building or using iperf3. Those are best directed towards the Discussions section for this project at https://github.com/esnet/iperf/discussions or to the iperf3 mailing list at iperf-dev@googlegroups.com. A list of frequently-asked questions regarding iperf3 can be found at http://software.es.net/iperf/faq.html.

Context

• Version of iperf3: iperf3.12

• Hardware: NA

• Operating system (and distribution, if any): Linux

Please note: iperf3 is supported on Linux, FreeBSD, and macOS. Support may be provided on a best-effort basis to other UNIX-like platforms. We cannot provide support for building and/or running iperf3 on Windows, iOS, or Android.

• Other relevant information (for example, non-default compilers, libraries, cross-compiling, etc.):

Please fill out one of the "Bug Report" or "Enhancement Request" sections, as appropriate. Note that submissions of bug fixes, new features, etc. should be done as a pull request at https://github.com/esnet/iperf/pulls

Bug Report

• Expected Behavior

• Actual Behavior

• Steps to Reproduce

• Possible Solution

Enhancement Request

For many testing purposes the omit option should allow to omit more than 60 seconds

• Current behavior

• Omit allows to put max 60 seconds

• Desired behavior

• Omit allows to put any int value in seconds

• Implementation notes

[davidBar-On]

Can you explain why do you need more than 60 seconds for the omit period? If I understand correctly, the main reason for the omit period is not to include in the statistics the initial connection period, since initially the throughput, etc. may fluctuate. Usually, few seconds are sufficient for that.

[tblaszcz]

Hello, Thank you for quick answer. The reason is to get tput only for some specific period of time or to get tput only from the end of iperf connection. Not related to slow start but some external features activity impacting the connection throughput. Due to some internal conditions the feature cannot be activated in first 60 seconds of the iperf. Because of that I need to omit more time to be sure that the tput is calculated for the time when feature is active. I can imagine more cases like this. Please let me know if you can consider extending the omit time. Thanks a lot.

[davidBar-On]

Submitted PR #1774 which extends the --omit limit to the same limit as --time (86,400 seconds). I don't know if and when this PR will be merged into the main line, but you may use its code to build a private version.