diff options
| author |   Tibor Frank <tifrank@cisco.com> | 2020-02-25 10:11:10 +0100 |
|---|---|---|
| committer | Tibor Frank <tifrank@cisco.com> | 2020-02-25 10:14:29 +0100 |
| commit | 84ab8bd624aa016988fc9f56e5a07e9ec07128b5 (patch) | |
| tree | e57cd81de1eac98568324bd43cfb83f6cc3680c5 /docs/report/introduction/methodology_tcp_with_iperf3.rst | |
| parent | 384c0d7196654cc32625024e75d616ae5175e1d5 (diff) | |
Report: Hoststack methodology
Change-Id: I105e1d4823df42522bff1af50d1bb173cd84d958
Signed-off-by: Tibor Frank <tifrank@cisco.com>
Diffstat (limited to 'docs/report/introduction/methodology_tcp_with_iperf3.rst')
| -rw-r--r-- | docs/report/introduction/methodology_tcp_with_iperf3.rst | 41 |
1 files changed, 0 insertions, 41 deletions
diff --git a/docs/report/introduction/methodology_tcp_with_iperf3.rst b/docs/report/introduction/methodology_tcp_with_iperf3.rst deleted file mode 100644 index 288da004a5..0000000000 --- a/docs/report/introduction/methodology_tcp_with_iperf3.rst +++ /dev/null @@ -1,41 +0,0 @@ -Hoststack Throughput Testing over 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 -Stack connection across two instances of VPP running on separate DUT -nodes. iperf3 is a popular open source tool for active measurements -of the maximum achievable goodput on IP networks. - -Because iperf3 utilizes the POSIX socket interface APIs, the current -test configuration utilizes the LD_PRELOAD mechanism in the linux -kernel to connect iperf3 to the VPP Host Stack using the VPP -Communications Library (VCL) LD_PRELOAD library (libvcl_ldpreload.so). - -In the future, a forked version of iperf3 which has been modified to -directly use the VCL application APIs may be added to determine the -difference in performance of 'VCL Native' applications versus utilizing -LD_PRELOAD which inherently has more overhead and other limitations. - -The test configuration is as follows: - - DUT1 Network DUT2 -[ iperf3-client -> VPP1 ]=======[ VPP2 -> iperf3-server] - -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. |