1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
Release Notes
=============
Changes in |csit-release|
-------------------------
#. VPP PERFORMANCE TESTS
- CSIT test environment is versioned, see
:ref:`test_environment_versioning`.
- **GENEVE tests**: Added VPP performance tests for GENEVE tunnels.
- See :ref:`geneve_methodology` for more details.
- **NAT44 tests**: Added new test type, pure throughput tests.
They are similar to PPS tests, but they employ ramp-up trials
to ensure all sessions are created (and not timing out)
for performance trials.
- **Jumbo for ipsec**: Test cases with 9000 byte frames are re-enabled
in ipsec suites.
- **Randomized profiles**: Improved repeatability and cycle length.
For details, see :ref:`packet_flow_ordering`.
- **AMD 2n-tx2 testbed**: New physical testbed type installed in
FD.io CSIT, with VPP and DPDK performance data added to CSIT
trending and this report.
#. TEST FRAMEWORK
- **TRex ASTF**: Improved capability to run TRex in advanced stateful mode.
- **CSIT PAPI support**: Due to issues with PAPI performance, VAT is
still used in CSIT for all VPP scale tests. See known issues below.
- **General Code Housekeeping**: Ongoing code optimizations,
speed ups and bug fixes.
#. PRESENTATION AND ANALYTICS LAYER
- **Graphs improvements**: Updated Packet Latency graphs,
see :ref:`latency_methodology`.
.. raw:: latex
\clearpage
.. _vpp_known_issues:
Known Issues
------------
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 | `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-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. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
Root Cause Analysis for Performance Changes
-------------------------------------------
List of RCAs in |csit-release| for VPP performance changes:
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| # | JiraID | Issue Description |
+====+=========================================+===========================================================================================================+
| 1 | | |
| | | |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
|
