X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Fvpp_performance_tests%2Fcsit_release_notes.rst;h=0914d9f4da30478f4c754eaa2180068f76d72f8c;hp=8fd8a3b63440db4ec8880d62089d3f972a00805a;hb=202f199be94d87144384f3ea9c6d50e9766b0d73;hpb=1261ada9edd22c784a7763d861c5acf87ccd1ae1 diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst index 8fd8a3b634..0914d9f4da 100644 --- a/docs/report/vpp_performance_tests/csit_release_notes.rst +++ b/docs/report/vpp_performance_tests/csit_release_notes.rst @@ -4,43 +4,38 @@ CSIT Release Notes Changes in CSIT |release| ------------------------- -#. Added VPP performance tests +#. **Added VPP performance tests** - - **Container Service Chain Topologies Orchestrated by K8s with VPP Memif** + - *MRR tests :* New MRR tests measure the packet forwarding rate + under the maximum load offered by traffic generator over a set + trial duration, regardless of packet loss. Maximum load for + specified Ethernet frame size is set to the bi-directional link + rate. MRR tests are used for continuous performance trending and + for comparison between releases. - - Added tests with VPP vswitch in container connecting a number of VPP- - in-container service chain topologies with L2 Cross-Connect and L2 - Bridge-Domain configurations, orchestrated by Kubernetes. Added - following forwarding topologies: i) "Parallel" with packets flowing from - NIC via VPP to container and back to VPP and NIC; ii) "Chained" (a.k.a. - "Snake") with packets flowing via VPP to container, back to VPP, to next - container, back to VPP and so on until the last container in a chain, - then back to VPP and NIC; iii) "Horizontal" with packets flowing via VPP - to container, then via "horizontal" memif to next container, and so on - until the last container, then back to VPP and NIC; + - *Service Chaining with SRv6 :* SRv6 (Segment Routing IPv6) proxy tests + verifying performance of Endpoint to SR-unaware appliance via + masquerading (End.AM), dynamic proxy (End.AD) or static proxy (End.AS) + functions. - - **MRR tests** +#. **Presentation and Analytics Layer (PAL)** - - ; + - Added continuous performance measuring, trending and anomaly + detection. Includes new PAL code and Jenkins jobs for Performance + Trending (PT) and Performance Analysis (PA) producing performance + trending dashboard and trendline graphs with summary and drill- + down views across all specified tests that can be reviewed and + inspected regularly by FD.io developers and users community. - - **SRv6** +#. **Test Framework Optimizations** - - Initial SRv6 (Segment Routing IPv6) tests verifying performance of - IPv6 and SRH (Segment Routing Header) encapsulation, decapsulation, - lookups and rewrites based on configured End and End.DX6 SRv6 egress - functions; + - *Performance tests efficiency :* Qemu build/install + optimizations, warmup phase handling, vpp restart handling. + Resulted in improved stability and reduced total execution time by + 30% for single pkt size e.g. 64B/78B. -#. Presentation and Analytics Layer - - - Added throughput speedup analysis for multi-core and multi-thread - VPP tests into Presentation and Analytics Layer (PAL) for automated - CSIT test results analysis; - -#. Other changes - - - **Framework optimizations** - - - Performance test duration improvements and stability; + - *General code housekeeping :* ongoing RF keywords + optimizations, removal of redundant RF keywords. Performance Changes ------------------- @@ -78,10 +73,6 @@ pretty ASCII formats: - `pretty ASCII format for 1t1c <../_static/vpp/performance-changes-pdr-1t1c-full.txt>`_, - `pretty ASCII format for 2t2c <../_static/vpp/performance-changes-pdr-2t2c-full.txt>`_. -Measured improvements are in line with VPP code optimizations listed in -`VPP-18.01 release notes -`_. - MRR Throughput Changes ~~~~~~~~~~~~~~~~~~~~~~ @@ -95,6 +86,24 @@ pretty ASCII formats: - `pretty ASCII format for 2t2c <../_static/vpp/performance-changes-mrr-2t2c-full.txt>`_, - `pretty ASCII format for 4t4c <../_static/vpp/performance-changes-mrr-4t4c-full.txt>`_. +Throughput Trending +------------------- + +In addition to reporting throughput changes between VPP releases, CSIT provides +continuous performance trending for VPP master branch: + +#. `VPP Performance Dashboard `_ +- per VPP test case throughput trend, trend compliance and summary of detected +anomalies. + +#. `Trending Methodology `_ +- throughput test metrics, trend calculations and anomaly classification +(progression, regression, outlier). + +#. `Trendline Graphs `_ +- per VPP build MRR throughput measurements against the trendline with anomaly +highlights, with associated CSIT test jobs. + Known Issues ------------ @@ -103,25 +112,22 @@ Here is the list of known issues in CSIT |release| for VPP performance tests: +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ | # | Issue | Jira ID | Description | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 1 | Vic1385 and Vic1227 low performance. | VPP-664 | Low NDR performance. | -| | | | | -+---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 2 | Sporadic (1 in 200) NDR discovery test failures | CSIT-570 | DPDK reporting rx-errors, indicating L1 issue. Suspected issue | +| 1 | Sporadic (1 in 200) NDR discovery test failures | CSIT-570 | DPDK reporting rx-errors, indicating L1 issue. Suspected issue | | | on x520. | | with HW combination of X710-X520 in LF testbeds. Not observed | | | | | outside of LF testbeds. | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 3 | Lower than expected NDR throughput with | CSIT-571 | Suspected NIC firmware or DPDK driver issue affecting NDR and | -| | xl710 and x710 NICs, compared to x520 NICs. | | PDR throughput. Applies to XL710 and X710 NICs. | +| 2 | Lower than expected NDR throughput of DPDK | CSIT-571 | Suspected NIC firmware or DPDK driver issue affecting NDR and | +| | testpmd and VPP L2 path NDR throughput with | | PDR throughput on XL710 and X710 NICs. | +| | xl710 and x710 NICs, compared to x520 NICs. | | | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 4 | rls1801 plugin related performance regression | CSIT-925 | With all plugins loaded NDR, PDR and MaxRates vary | -| | | | intermittently from 3% to 5% across multiple test executions. | -| | | | Requires plugin code bisecting. | +| 3 | Tagged Ethernet dot1q and dot1ad L2 path | CSIT-1066 | Tagged Ethernet dot1q and dot1ad L2 path throughput regression: | +| | throughput regression. | | NDR -2%..-5%, PDR -2%..-6%, MRR. Affects l2xc and l2bd | +| | | | performance tests. | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 5 | rls1801 generic small performance regression | CSIT-926 | Generic performance regression of discovered NDR, PDR and | -| | ip4base, l2xcbase, l2bdbase | | MaxRates of -3%..-1% vs. rls1710, affects ip4base, l2xcbase, | -| | | | l2bdbase test suites. Not detected by CSIT performance trending | -| | | | scheme as it was masked out by another issue CSIT-925. | +| 4 | IPSec (software, no QAT HW) throughput | CSIT-1064 | IPSec throughput regression: NDR -3%..-8%, PDR -2%..-8%, MRR | +| | regression. | | -3%..-7%. | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+ -| 6 | rls1801 substantial NDR/PDR regression for | CSIT-928 | NDR regression of -7%..-15%, PDR regression of -3%..-15% | -| | IPSec tunnel scale with HW QAT crypto-dev | | compared to rls1710. | +| 5 | High failure rate of creating working container | CSIT-1065 | Orchestrated container topology tests failing data plane | +| | topologies with K8s/Ligato orchestration. | | verification indicating configuration issue. Suspected issue | +| | | | with Ligato vpp-agent. | +---+-------------------------------------------------+------------+-----------------------------------------------------------------+