...
Expand | ||
---|---|---|
| ||
Overview
WiscNet Server Details
|
Note |
---|
Please note: The hardware performance of the client running this test has a significant impact on results WiscNet has noticed that the Iperf clients for Linux, Unix, and macOS perform better than the ports for Windows |
...
Enter iperf -h or man iperf depending on your operating system. Here are some common flags:
...
-b 250m
...
-L
...
-r
...
-d
...
TCP vs UDP testing
Iperf uses TCP by default. TCP has built in congestion avoidance. If TCP detects any packet loss, it assumes that the link capacity has been reached, and it slows down. This works very well, unless there is packet loss caused by something other than congestion. If there is packet loss due to errors, TCP will back off even if there is plenty of capacity. iperf allows TCP to send as fast as it can, which generally works to fill a clean, low latency link with packets. If a path is not clean/error free or has high latency, TCP will have a difficult time filling it. For testing higher capacity links and for links with higher latency, you will want to adjust the window size (-w option).
...
TCP vs UDP Testing
|
Note |
---|
Please note: The hardware performance of the client running this test has a significant impact on results WiscNet has noticed that the Iperf clients for Linux, Unix, and macOS perform better than the ports for Windows |
Some common Iperf flags
Enter iperf -h or man iperf depending on your operating system. Here are some common flags:
Flag | Details | Example |
---|---|---|
-c | Client mode | -c |
-t | Time to run the test in seconds | -t 30 |
-P | Number of parallel connections | -P 2 |
-u | UDP (default is TCP) | -u |
-b | Bandwidth per thread | -b 250m |
-i | Interval between bandwidth reports in seconds | -i 1 |
-L | Listen on port | -L 5001 |
-r | bidirectional test (individually) | -r |
-d | bidirectional test (simultaneously) | -d |
Examples
Unidirectional UDP 1Gbps circuit test
...