- 1. iperf3 server attaches to VPP2 and LISTENs on VPP2:TCP port 5201.
- 2. iperf3 client attaches to VPP1 and opens one or more stream
- connections to VPP2:TCP port 5201.
- 3. iperf3 client transmits a uni-directional stream as fast as the
- VPP Host Stack allows to the iperf3 server for the test duration.
- 4. At the end of the test the iperf3 client emits the goodput
- measurements for all streams and the sum of all streams.
-
- Test cases include 1 and 10 Streams with a 20 second test duration
- with the VPP Host Stack configured to utilize the Cubic TCP
- congestion algorithm.
-
- Note: iperf3 is single threaded, so it is expected that the 10 stream
- test does not show any performance improvement due to
- multi-thread/multi-core execution.
+1. iperf3 server attaches to VPP2 and LISTENs on VPP2:TCP port 5201.
+2. iperf3 client attaches to VPP1 and opens one or more stream
+ connections to VPP2:TCP port 5201.
+3. iperf3 client transmits a uni-directional stream as fast as the
+ VPP Host Stack allows to the iperf3 server for the test duration.
+4. At the end of the test the iperf3 client emits the goodput
+ measurements for all streams and the sum of all streams.
+
+Test cases include 1 and 10 Streams with a 20 second test duration
+with the VPP Host Stack configured to utilize the Cubic TCP
+congestion algorithm.
+
+Note: iperf3 is single threaded, so it is expected that the 10 stream
+test shows little or no performance improvement due to
+multi-thread/multi-core execution.
+
+There are also variations of these test cases which use the VPP Network
+Simulator (NSIM) plugin to test the VPP Hoststack goodput with 1 percent
+of the traffic being dropped at the output interface of VPP1 thereby
+simulating a lossy network. The NSIM tests are experimental and the
+test results are not currently representative of typical results in a
+lossy network.