perfSONAR User Q&A and Other Discussion

[Bob McMahon <>]

Also, for TCP, later version of iperf 2 supports -b on the client (transmitter) using a very simple token bucket.   The token bucket depth is "unlimited" though.

I'm considering two things,

1) Limiting the token bucket depth based on four times the -i interval, if none then no limit

2) Adding token bucket support for the server (read)

For kernel level traffic shaping w/linux, linux traffic control can be used.  

I think all the techniques have advantages and disadvantages depending upon the goals of the testing.

Bob

On Sun, May 14, 2017 at 3:18 PM, Brian Tierney <> wrote:

-b works for both TCP and UDP, but --fq-rate works much better for TCP on CentOS7/Debian8 based hosts, as it does kernel-level pacing, not user-level pacing.

On Sat, May 13, 2017 at 7:54 PM, Arman Mohsin <> wrote:

Hi Brian,

Hope all is well. Does the iperf3 -c -b option limit bandwidth for TCP as well or is it ONLY for UDP? I tried to read the documentation in the man page but it is a bit confusing. In the earlier versions of iperf the -b option is used to test only UDP but I am not sure if it supports in the latest version (iperf3)

Regards,

Arman

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iperf-users mailing list

https://lists.sourceforge.net/lists/listinfo/iperf-users