diff options
author | Vratko Polak <vrpolak@cisco.com> | 2020-02-26 18:19:48 +0100 |
---|---|---|
committer | Tibor Frank <tifrank@cisco.com> | 2020-03-03 10:05:30 +0000 |
commit | 827ed3c36c2d789dc3fd0f41cc17de1587416103 (patch) | |
tree | d542bc2ed3edac499fcf81ec1f5063bfaa6813c9 /docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst | |
parent | 3fb7e3f7b0c51c0329c5f7192997778eb1dd5709 (diff) |
Improve hoststack methodology pages
+ Also update corresponding chapter names for results.
- Kept picotls there as in future we may have others.
Change-Id: Ib8037740ebbb2a517e31cc62dfc6a423eb126cba
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Signed-off-by: Dave Wallace <dwallacelf@gmail.com>
Diffstat (limited to 'docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst')
-rw-r--r-- | docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst | 39 |
1 files changed, 22 insertions, 17 deletions
diff --git a/docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst b/docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst index 1355a3cb21..e0d3e2435f 100644 --- a/docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst +++ b/docs/report/introduction/methodology_hoststack_testing/methodology_tcp_with_iperf3.rst @@ -1,5 +1,5 @@ -Hoststack Throughput Testing over TCP/IP with iperf3 -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +TCP/IP with iperf3 +^^^^^^^^^^^^^^^^^^ `iperf3 goodput measurement tool <https://github.com/esnet/iperf>`_ is used for measuring the maximum attainable goodput of the VPP Host @@ -26,18 +26,23 @@ The test configuration is as follows: where, - 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 does not show any 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. |