- CSIT test environment is versioned, see
:ref:`test_environment_versioning`.
- CSIT test environment is versioned, see
:ref:`test_environment_versioning`.
- - 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`.
+ - **GENEVE tests**: Added VPP performance tests for GENEVE tunnels.
- - 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.
+ - **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.
- - 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.
+ - **Randomized profiles**: Improved repeatability and cycle length.
+ For details, see :ref:`packet_flow_ordering`.
- - **IPSec async mode tests**: Added VPP performance tests for async crypto
- engine.
+ - **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.
- - **AMD 2n-zn2 testbed**: New physical testbed type installed in FD.io CSIT,
- VPP performance data will be added in upcoming weeks.
+ - **Framework speedup**: Shortened overall test job duration
+ by using a different test selection mechanism (using --test
+ instead of --include) and by avoiding unnecessary PAPI reconnects.
- **CSIT PAPI support**: Due to issues with PAPI performance, VAT is
still used in CSIT for all VPP scale tests. See known issues below.
- **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 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.
+ - **General Code Housekeeping**: Ongoing code optimizations,
+ speed ups and bug fixes.
- - **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.
+ - **Graphs improvements**: Updated Packet Latency graphs,
+ see :ref:`latency_methodology`.
| | `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. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | `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. |
+| 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. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | <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. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+