X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Fnew%2Fcpta%2Fintroduction%2Findex.rst;fp=docs%2Fnew%2Fcpta%2Fintroduction%2Findex.rst;h=016037b067c5580a37ff1d24894d4ecdffc571b4;hb=06ffc53e2b8cc99d3fe30925ac34b5ba543db048;hp=0000000000000000000000000000000000000000;hpb=801499cd0cceeb1c98ee36d606b883041d8e046c;p=csit.git diff --git a/docs/new/cpta/introduction/index.rst b/docs/new/cpta/introduction/index.rst new file mode 100644 index 0000000000..016037b067 --- /dev/null +++ b/docs/new/cpta/introduction/index.rst @@ -0,0 +1,54 @@ +VPP Performance Dashboard +========================= + +Description +----------- + +Performance dashboard tables provide the latest VPP throughput trend, +trend compliance and detected anomalies, all on a per VPP test case +basis. Linked trendline graphs enable further drill-down into the +trendline compliance, sequence and nature of anomalies, as well as +pointers to performance test builds/logs and VPP builds. Performance +trending is currently based on the Maximum Receive Rate (MRR) tests. MRR +tests measure the packet forwarding rate under the maximum load offered +by traffic generator over a set trial duration, regardless of packet +loss. See :ref:`trending_methodology` section for more detail including +trend and anomaly calculations. + +Data samples are generated by the CSIT VPP performance trending jobs +executed twice a day (target start: every 12 hrs, 02:00, 14:00 UTC). All +trend and anomaly evaluation is based on a rolling window of data +samples, covering last 7 days. + +Legend to table: + + - **Test Case** : name of FD.io CSIT test case, naming convention + `here `_. + - **Trend [Mpps]** : last value of performance trend. + - **Short-Term Change [%]** : Relative change of last trend value + vs. last week trend value. + - **Long-Term Change [%]** : Relative change of last trend value vs. + maximum of trend values over the last quarter except last week. + - **Regressions [#]** : Number of regressions detected. + - **Progressions [#]** : Number of progressions detected. + - **Outliers [#]** : Number of outliers detected. + +Tested VPP worker-thread-core combinations (1t1c, 2t2c, 4t4c) are listed +in separate tables in section 1.x. Followed by trending methodology in +section 2. and trendline graphs in sections 3.x. Performance test data +used for trendline graphs is provided in sections 4.x. + +VPP worker on 1t1c +------------------ + +.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-1t1c.rst + +VPP worker on 2t2c +------------------ + +.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-2t2c.rst + +VPP worker on 4t4c +------------------ + +.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-4t4c.rst