#. VPP PERFORMANCE TESTS
- - **Service density 2n-skx tests**: Added higher NF density tests with two
- NFs' data-plane threads sharing a physical core. VPP IPv4 routing is now
- used as a VNF payload similar to CNF tests.
+ - CSIT test environment is versioned, see
+ :ref:`test_environment_versioning`.
- - **Soak Tests**: Optimized performamce soak tests framework
- code for extended time duration tests and throughput discovery
- at given PLR and at give total test time e.g. minutes, hours,
- days, weeks. See updated
- :ref:`test_methodology` section for more details.
+ - To identify performance changes due to VPP code changes from
+ v20.05.0 to v20.09.0, both have been tested in CSIT environment
+ ver. 5 and compared against each other. All substantial
+ progressions has been marked up with RCA analysis. See
+ :ref:`vpp_compare_current_vs_previous_release` and
+ :ref:`vpp_known_issues`.
-#. TEST FRAMEWORK
+ - **NAT44 tests**: Adapted existing and added new tests.
- - **Qemu code refactor**: Complete code refactor of the key components of
- QemuUtil.py and QemuManager.py (L1 and L2 KW counterparts). Added
- implementation of kernel-image-kvm based VM replacing the previously used
- NestedVM images. Added ability to run VPP as a payload in VNF.
+ - Refactored NAT44 deterministic mode (nat44det) tests to use separate
+ det44 vpp plugin and to use the same scheme of inside and outside
+ addresses and ports, as used in new NAT44 endpoint-dependent mode tests.
- - **CSIT PAPI Support**: Continued conversion of CSIT VAT L1 keywords to
- PAPI L1 KWs in CSIT using VPP Python bindings. Redesign of key components
- of PAPI Executor and PAPI history.
+ - Added new NAT44 endpoint-depended mode uni-directional (nat44ed-udir)
+ tests that measure packet throughput in one direction with usage of TRex
+ in stateless mode.
- - **General Code Housekeeping**: Ongoing RF keywords optimizations,
- removal of redundant RF keywords.
+ - Added new NAT44 endpoint-dependent mode CPS tests that measure
+ connections per second with usage of TRex in stateful mode.
+ NOTE: CPS measurement data will be added in two weeks.
- - **Test suite generator**: Added capability to generate suites for
- different NIC models as well as throughput search algorithm types. Uses
- base tests suites as source.
+ - **IPSec async mode tests**: Added VPP performance tests for async crypto
+ engine.
- - **TOX verification**: Added verifications for test suite generator.
+ - **AMD 2n-zn2 testbed**: New physical testbed type installed in FD.io CSIT,
+ VPP performance data will be added in upcoming weeks.
-#. PRESENTATION AND ANALYTICS LAYER
+#. TEST FRAMEWORK
+
+ - **TRex ASTF**: Added capability to run TRex in advanced stateful mode.
- - **Graphs Layout Improvements**: Improved performance graphs layout
- for better readibility and maintenance: test grouping, axis
- labels, descriptions, other informative decoration.
+ - **CSIT PAPI support**: Due to issues with PAPI performance, VAT is
+ still used in CSIT for all VPP scale tests. See known issues below.
-..
- #. MISCELLANEOUS
+ - **General Code Housekeeping**: Ongoing RF keywords optimizations,
+ removal of redundant RF keywords and aligning of suite/test
+ setup/teardowns.
+
+ - **Intel E810CQ 100G NIC**: Added configuration for Intel E810CQ 100G NIC.
+ No tests run for this NIC as it is not present in FD.io CSIT lab yet.
+
+#. PRESENTATION AND ANALYTICS LAYER
- - **2n-dnv Tests (3rd Party)**: Published performance tests for 2n-
- dnv (2-Node Atom Denverton) from 3rd party testbeds running FD.io
- |csit-release| automated testing code.
- Only graphs for Packet Throughput and Speedup Multi-core and not
- for Packet Latency were published as there are no results for Packet
- Latency available.
+ - **Graphs improvements**: Added possibility to use Gbps on Y-axis in
+ Packet Throughput and Speedup Multi-Core graphs, added unidirectional
+ mode to the Latency graphs.
.. raw:: latex
List of known issues in |csit-release| for VPP performance tests:
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| # | JiraID | Issue Description |
-+====+=========================================+==========================================================================================================+
-| 1 | `CSIT-570 | Sporadic (1 in 200) NDR discovery test failures on x520. DPDK reporting rx-errors, indicating L1 issue. |
-| | <https://jira.fd.io/browse/CSIT-570>`_ | Suspected issue with HW combination of X710-X520 in LF testbeds. Not observed outside of LF testbeds. |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| 2 | `CSIT-1503 | [`TRex-519 <https://trex-tgn.cisco.com/youtrack/issue/trex-519>`_] XL710/XXV710 with FW 6.0.1 will have |
-| | <https://jira.fd.io/browse/CSIT-1503>`_ | Rx drop rate of 27MPPS. |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| 3 | `CSIT-1501 | Sporadic crypto backend fails loading `VPP-1670 <https://jira.fd.io/browse/VPP-1670>`_ |
-| | <https://jira.fd.io/browse/CSIT-1501>`_ | |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| 4 | `CSIT-1427 | Sporadic HW aes-128-cbc-sha1 tunnel-interface tests are failing. |
-| | <https://jira.fd.io/browse/CSIT-1427>`_ | `VPP-1671 <https://jira.fd.io/browse/VPP-1671>`_ |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| 5 | `CSIT-1498 | Memif tests are sporadically failing on initialization of memif connection. |
-| | <https://jira.fd.io/browse/CSIT-1498>`_ | |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
-| 6 | `CSIT-1499 | AVF tests are sporadically failing on initialization of AVF interface. |
-| | <https://jira.fd.io/browse/CSIT-1499>`_ | |
-+----+-----------------------------------------+----------------------------------------------------------------------------------------------------------+
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| # | JiraID | Issue Description |
++====+=========================================+===========================================================================================================+
+| 1 | `CSIT-570 | Sporadic (1 in 200) NDR discovery test failures on x520. DPDK reporting rx-errors, indicating L1 issue. |
+| | <https://jira.fd.io/browse/CSIT-570>`_ | Suspected issue with HW combination of X710-X520 in LF testbeds. Not observed outside of LF testbeds. |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 2 | `VPP-662 | 9000B packets not supported by NICs VIC1227 and VIC1387. |
+| | <https://jira.fd.io/browse/VPP-662>`_ | |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 3 | `CSIT-1763 | Adapt ramp-up phase of nat44 tests for different frame sizes. |
+| | <https://jira.fd.io/browse/CSIT-1763>`_ | Currently ramp-up phase rate and duration values are correctly set for tests with 64B frame size. |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 4 | `CSIT-1671 | All CSIT scale tests can not use PAPI due to much slower performance compared to VAT/CLI (it takes much |
+| | <https://jira.fd.io/browse/CSIT-1671>`_ | longer to program VPP). This needs to be addressed on the PAPI side. |
+| +-----------------------------------------+ The usual PAPI library spends too much time parsing arguments, so even with async processing (hundreds of |
+| | `VPP-1763 | commands in flight over socket), the VPP configuration for large scale tests (millions of messages) takes |
+| | <https://jira.fd.io/browse/VPP-1763>`_ | too long. |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 5 | `VPP-1675 | IPv4 IPSEC 9000B packet tests are failing as no packet is forwarded. |
+| | <https://jira.fd.io/browse/VPP-1675>`_ | Reason: chained buffers are not supported. |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 6 | `VPP-1934 | [i40e] Interfaces are not brought up from carrier-down. |
+| | <https://jira.fd.io/browse/VPP-1934>`_ | In case of i40e -based interface (e.g Intel x700 series NIC) is bound to kernel driver (i40e) and is in |
+| | | state "no-carrier" (<NO-CARRIER,BROADCAST,MULTICAST,UP>) because previously it was disabled via |
+| | | "I40E_AQ_PHY_LINK_ENABLED" call, then VPP during initialization of AVF interface is not re-enabling |
+| | | interface link via i40e driver to up. |
+| | | CSIT implemented `workaround for AVF interface <https://gerrit.fd.io/r/c/csit/+/29086>`_ until fixed. |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| 7 | `CSIT-1760 | All Mellanox / rdma driver tests are failing on LF testbed28 while successfully run on other LF testbeds. |
+| | <https://jira.fd.io/browse/CSIT-1760>`_ | |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+
+Root Cause Analysis for Performance Changes
+-------------------------------------------
+
+List of RCAs in |csit-release| for VPP performance changes:
+
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| # | JiraID | Issue Description |
++====+=========================================+===========================================================================================================+
+| 1 | | |
+| | | |
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+