1 .. _vpp_performance_tests_release_notes:
6 Changes in |csit-release|
7 -------------------------
9 #. VPP PERFORMANCE TESTS
11 - **Intel Xeon Ice Lake**: Performance test data for these platforms
12 continues to be provided by external Intel benchmarking labs
13 executing |csit-release| tests. For details about the physical
14 setup see :ref:`tested_physical_topologies`.
16 - **AWS EC2 c5n**: Performance test data for AWS c5n instances has
17 been added to report for ip4, ip6 and ipsec tests.
19 - **Reduction of tests**: Removed certain test variations executed
20 iteratively for the report (as well as in daily and weekly
21 trending) due to physical testbeds overload.
25 - **CSIT test environment** version has been updated to ver. 8, see
26 :ref:`test_environment_versioning`.
28 - **CSIT in AWS environment**: Completed CSIT automation support for
29 AWS c5n instances environment, including weekly performance
30 trending tests execution.
32 - **CSIT PAPI support**: Due to issues with PAPI performance, and
33 deprecation of VAT, CLI is used in CSIT for many VPP scale tests.
34 See known issues below.
36 - **General Code Housekeeping**: Ongoing code optimizations and bug
39 #. PRESENTATION AND ANALYTICS LAYER
41 - **Graphs improvements**: Updated Packet Latency graphs,
42 see :ref:`latency_methodology`.
56 Issues reported in previous releases which were fixed in this release:
58 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
59 | # | JiraID | Issue Description |
60 +====+=========================================+===========================================================================================================+
61 | 1 | `CSIT-1789 | AVF driver does not perform RSS in a deterministic way. |
62 | | <https://jira.fd.io/browse/CSIT-1789>`_ | VPP now uses the same RSS key with AVF driver as with DPDK driver. |
63 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
64 | 2 | `CSIT-1786 | IP4 and IP6 scale tests failing with no traffic forwarded. |
65 | | <https://jira.fd.io/browse/CSIT-1786>`_ | CSIT replaced the old single VAT command by file full of "exec" CLI commands executed by VAT. |
66 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
71 Issues reported in previous releases which still affect the current results.
73 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
74 | # | JiraID | Issue Description |
75 +====+=========================================+===========================================================================================================+
76 | 3 | `CSIT-1782 | Multicore AVF tests are failing when trying to create interface. |
77 | | <https://jira.fd.io/browse/CSIT-1782>`_ | Frequency is reduced by s CSIT workaround, but occasional failures do still happen. |
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 | +-----------------------------------------+ Currently, the time critical code uses VAT running large files with exec statements and CLI commands. |
82 | | `VPP-1763 | Still, we needed to reduce the number of scale tests run to keep overall duration reasonable. |
83 | | <https://jira.fd.io/browse/VPP-1763>`_ | More improvements needed to achieve sufficient configuration speed. |
84 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
85 | 5 | `CSIT-1789 | IPSEC SW async scheduler tests show bad behavior. |
86 | | <https://jira.fd.io/browse/CSIT-1789>`_ | VPP code is not behaving correctly when crypto workers are the bottleneck. |
87 | +-----------------------------------------+ |
89 | | <https://jira.fd.io/browse/VPP-1998>`_ | |
90 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
91 | 6 | `CSIT-1785 | NAT44ED tests failing to establish all TCP sessions. |
92 | | <https://jira.fd.io/browse/CSIT-1785>`_ | At least for max scale, in allotted time (limited by session 500s timeout) due to worse |
93 | +-----------------------------------------+ slow path performance than previously measured and calibrated for. |
94 | | `VPP-1972 | CSIT removed the max scale NAT tests to avoid this issue. |
95 | | <https://jira.fd.io/browse/VPP-1972>`_ | |
96 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
97 | 7 | `CSIT-1791 | Performance regression in RDMA tests, due to CSIT environment changes. |
98 | | <https://jira.fd.io/browse/CSIT-1791>`_ | Two symptoms: 1. 10-20% regression across most tests. 2. DUT performance cap just below 38 Mpps. |
99 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
104 No new issues appeared in |csit-release| for VPP performance tests,
105 except for the performance changes listed below.
107 Root Cause Analysis for Performance Changes
108 -------------------------------------------
110 List of RCAs in |csit-release| for VPP performance changes:
112 +----+-----------------------------------------+------------------------------------------------------------+
113 | # | JiraID | Issue Description |
114 +====+=========================================+============================================================+
115 | 0 | | To be updated when descriptions in Jira tickets are ready. |
116 +----+-----------------------------------------+------------------------------------------------------------+