4 Changes in |csit-release|
5 -------------------------
7 #. VPP PERFORMANCE TESTS
9 - CSIT test environment is versioned, see
10 :ref:`test_environment_versioning`.
12 - **GENEVE tests**: Added VPP performance tests for GENEVE tunnels.
13 See :ref:`geneve_methodology` for more details.
16 - **GSO tests**: Added VPP performance tests for GSOtap and GSOvirtio.
17 All tested topologies are compared with GSO enabled and disabled.
18 In |csit-release| there is only 1t1c tests running.
19 See :ref:`gso_methodology` for more details.
22 - **NAT44 tests**: Added new test type, pure throughput tests.
23 They are similar to PPS tests, but they employ ramp-up trials
24 to ensure all sessions are created (and not timing out)
25 for performance trials.
27 - **Jumbo for ipsec**: Test cases with 9000 byte frames are re-enabled
30 - **Randomized profiles**: Improved repeatability and cycle length.
31 For details, see :ref:`packet_flow_ordering`.
33 - **Arm 2n-tx2 testbed**: New physical testbed type installed in
34 FD.io CSIT, with VPP and DPDK performance data added to CSIT
35 trending and this report.
37 - **Framework speedup**: Shortened overall test job duration
38 by using a different test selection mechanism (using --test
39 instead of --include) and by avoiding unnecessary PAPI reconnects.
43 - **TRex ASTF**: Improved capability to run TRex in advanced stateful mode.
45 - **CSIT PAPI support**: Due to issues with PAPI performance, VAT is
46 still used in CSIT for all VPP scale tests. See known issues below.
48 - **General Code Housekeeping**: Ongoing code optimizations,
49 speed ups and bug fixes.
51 #. PRESENTATION AND ANALYTICS LAYER
53 - **Graphs improvements**: Updated Packet Latency graphs,
54 see :ref:`latency_methodology`.
65 List of known issues in |csit-release| for VPP performance tests:
67 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
68 | # | JiraID | Issue Description |
69 +====+=========================================+===========================================================================================================+
70 | 1 | `CSIT-570 | Sporadic (1 in 200) NDR discovery test failures on x520. DPDK reporting rx-errors, indicating L1 issue. |
71 | | <https://jira.fd.io/browse/CSIT-570>`_ | Suspected issue with HW combination of X710-X520 in LF testbeds. Not observed outside of LF testbeds. |
72 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
73 | 2 | `VPP-662 | 9000B packets not supported by NICs VIC1227 and VIC1387. |
74 | | <https://jira.fd.io/browse/VPP-662>`_ | |
75 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
76 | 3 | `CSIT-1763 | Adapt ramp-up phase of nat44 tests for different frame sizes. |
77 | | <https://jira.fd.io/browse/CSIT-1763>`_ | Currently ramp-up phase rate and duration values are correctly set for tests with 64B frame size. |
78 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
79 | 4 | `CSIT-1671 | All CSIT scale tests can not use PAPI due to much slower performance compared to VAT/CLI (it takes much |
80 | | <https://jira.fd.io/browse/CSIT-1671>`_ | longer to program VPP). This needs to be addressed on the PAPI side. |
81 | +-----------------------------------------+ The usual PAPI library spends too much time parsing arguments, so even with async processing (hundreds of |
82 | | `VPP-1763 | commands in flight over socket), the VPP configuration for large scale tests (millions of messages) takes |
83 | | <https://jira.fd.io/browse/VPP-1763>`_ | too long. |
84 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
85 | 5 | `VPP-1934 | [i40e] Interfaces are not brought up from carrier-down. |
86 | | <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 |
87 | | | state "no-carrier" (<NO-CARRIER,BROADCAST,MULTICAST,UP>) because previously it was disabled via |
88 | | | "I40E_AQ_PHY_LINK_ENABLED" call, then VPP during initialization of AVF interface is not re-enabling |
89 | | | interface link via i40e driver to up. |
90 | | | CSIT implemented `workaround for AVF interface <https://gerrit.fd.io/r/c/csit/+/29086>`_ until fixed. |
91 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
93 Root Cause Analysis for Performance Changes
94 -------------------------------------------
96 List of RCAs in |csit-release| for VPP performance changes:
98 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
99 | # | JiraID | Issue Description |
100 +====+=========================================+===========================================================================================================+
101 | 1 | `VPP-1972 | One VPP change has decreased performance of NAT44ed processing, both slow path and fast path. |
102 | | <https://jira.fd.io/browse/VPP-1972>`_ | |
103 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+