No worries Bruce. Thanks for the correction. I'm older too so maybe being called older isn't really a bad thing ;)
I do think many users will learn each tool's feature set based upon their needs. Having two similar open source tools with some overlapping capabilities, e.g. to measure throughput or capacity, is a good thing for all. If one suspects the tool they can try the other one. I do think some core properties which both tools support are: - capacity measurements with CWND & RTT sampling (iperf2 requires -e) - --fq-rate based source pacing - support for threads Note: There may be a move towards TCP CCAs that support source pacing, as network hosts evolve from as fast as possible (AFAP) towards congestion mitigation, to help eliminate standing queues or bufferbloat. I've added some --fq-rate options that might be applicable to the iperf 3 user base - not sure. The iperf 2 pacing options include the below as well as supporting the CCA per client side only setting of --tcp-cca which get passed to the server (CCA's like prague need it set on both ends for the L4S ECN support.) *--tcp-cca*Set the congestion control algorithm to be used for TCP connections. (same as --tcp-congestion) *--fq-rate **n*[kmgKMG]Set a rate to be used with fair-queuing based socket-level pacing, in bytes or bits per second. Only available on platforms supporting the SO_MAX_PACING_RATE socket option. (Note: Here the suffixes indicate bytes/sec or bits/sec per use of uppercase or lowercase, respectively)*--fq-rate-step **n*[kmgKMG]Set a step of rate to be used with fair-queuing based socket-level pacing, in bytes or bits per second. Step occurs every fq-rate-step-interval (defaults to one second) *--fq-rate-step-interval **n*Time in seconds before stepping the fq-rate On Fri, Sep 15, 2023 at 1:35 PM Bruce A. Mah <[email protected]> wrote: > I've corrected our advisory and sent out a new version. > > Once again, sorry for giving the wrong impression. I believe this comes > from a copy-and-paste of some much earlier text that was written before you > started actively maintaining iperf2 (that does not excuse the error, but > that's probably why it happened). > > Bruce. > > I wrote: > > > Hi Bob-- > > > > Apologies! The text "older version" wasn't right and didn't even > contribute any value in the context where it was used. I'm not sure how > that phrase got included, but that mistake is definitely mine. > > > > Thanks for the update on iperf2 activities. We've been working on adding > multi-threading capabilities to iperf3, so that it can use multiple CPU > cores for higher throughput testing. (Of course, iperf2 has had this > ability for quite awhile.) We've done a few public betas over the summer, > with generally useful and favorable results. The plan is to bring this into > a mainline release "soon". > > > > Bruce. > > > > If memory serves me right, Bob McMahon wrote: > > > >> Thanks for this Bruce & to the iperf 3 team. > >> > >> A small correction - not sure I'd say iperf2 is an older version but > rather > >> another version based from the original iperf code (using those design > >> patterns.) The latest version for iperf 2 is version 2.1.9 released on > >> March 14, 2023. One can always compile the bleeding edge from source per > >> the master branch. Those commits come in spurts but can be daily. Some > new > >> multicast code was committed yesterday as an example. > > [snip] > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Iperf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iperf-users
