docs/report/vpp_performance_tests/csit_release_notes.rst

   1 Release Notes
   2 =============
   3
   4 Changes in |csit-release|
   5 -------------------------
   6
   7 #. VPP PERFORMANCE TESTS
   8
   9    - CSIT test environment is versioned, see
  10      :ref:`test_environment_versioning`.
  11
  12    - **GENEVE tests**: Added VPP performance tests for GENEVE tunnels.
  13
  14      - See :ref:`geneve_methodology` for more details.
  15
  16    - **NAT44 tests**: Added new test type, pure throughput tests.
  17      They are similar to PPS tests, but they employ ramp-up trials
  18      to ensure all sessions are created (and not timing out)
  19      for performance trials.
  20
  21    - **Jumbo for ipsec**: Test cases with 9000 byte frames are re-enabled
  22      in ipsec suites.
  23
  24    - **Randomized profiles**: Improved repeatability and cycle length.
  25      For details, see :ref:`packet_flow_ordering`.
  26
  27    - **AMD 2n-tx2 testbed**: New physical testbed type installed in
  28      FD.io CSIT, with VPP and DPDK performance data added to CSIT
  29      trending and this report.
  30
  31 #. TEST FRAMEWORK
  32
  33    - **TRex ASTF**: Improved capability to run TRex in advanced stateful mode.
  34
  35    - **CSIT PAPI support**: Due to issues with PAPI performance, VAT is
  36      still used in CSIT for all VPP scale tests. See known issues below.
  37
  38    - **General Code Housekeeping**: Ongoing code optimizations,
  39      speed ups and bug fixes.
  40
  41 #. PRESENTATION AND ANALYTICS LAYER
  42
  43    - **Graphs improvements**: Updated Packet Latency graphs,
  44      see :ref:`latency_methodology`.
  45
  46 .. raw:: latex
  47
  48     \clearpage
  49
  50 .. _vpp_known_issues:
  51
  52 Known Issues
  53 ------------
  54
  55 List of known issues in |csit-release| for VPP performance tests:
  56
  57 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  58 | #  | JiraID                                  | Issue Description                                                                                         |
  59 +====+=========================================+===========================================================================================================+
  60 |  1 | `CSIT-570                               | Sporadic (1 in 200) NDR discovery test failures on x520. DPDK reporting rx-errors, indicating L1 issue.   |
  61 |    | <https://jira.fd.io/browse/CSIT-570>`_  | Suspected issue with HW combination of X710-X520 in LF testbeds. Not observed outside of LF testbeds.     |
  62 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  63 |  2 | `VPP-662                                | 9000B packets not supported by NICs VIC1227 and VIC1387.                                                  |
  64 |    | <https://jira.fd.io/browse/VPP-662>`_   |                                                                                                           |
  65 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  66 |  3 | `CSIT-1763                              | Adapt ramp-up phase of nat44 tests for different frame sizes.                                             |
  67 |    | <https://jira.fd.io/browse/CSIT-1763>`_ | Currently ramp-up phase rate and duration values are correctly set for tests with 64B frame size.         |
  68 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  69 |  4 | `CSIT-1671                              | All CSIT scale tests can not use PAPI due to much slower performance compared to VAT/CLI (it takes much   |
  70 |    | <https://jira.fd.io/browse/CSIT-1671>`_ | longer to program VPP). This needs to be addressed on the PAPI side.                                      |
  71 |    +-----------------------------------------+ The usual PAPI library spends too much time parsing arguments, so even with async processing (hundreds of |
  72 |    | `VPP-1763                               | commands in flight over socket), the VPP configuration for large scale tests (millions of messages) takes |
  73 |    | <https://jira.fd.io/browse/VPP-1763>`_  | too long.                                                                                                 |
  74 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  75 |  5 | `VPP-1934                               | [i40e] Interfaces are not brought up from carrier-down.                                                   |
  76 |    | <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   |
  77 |    |                                         | state "no-carrier" (<NO-CARRIER,BROADCAST,MULTICAST,UP>) because previously it was disabled via           |
  78 |    |                                         | "I40E_AQ_PHY_LINK_ENABLED" call, then VPP during initialization of AVF interface is not re-enabling       |
  79 |    |                                         | interface link via i40e driver to up.                                                                     |
  80 |    |                                         | CSIT implemented `workaround for AVF interface <https://gerrit.fd.io/r/c/csit/+/29086>`_ until fixed.     |
  81 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  82
  83 Root Cause Analysis for Performance Changes
  84 -------------------------------------------
  85
  86 List of RCAs in |csit-release| for VPP performance changes:
  87
  88 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
  89 | #  | JiraID                                  | Issue Description                                                                                         |
  90 +====+=========================================+===========================================================================================================+
  91 |  1 |                                         |                                                                                                           |
  92 |    |                                         |                                                                                                           |
  93 +----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+