aboutsummaryrefslogtreecommitdiffstats
path: root/docs/cpta/introduction
diff options
context:
space:
mode:
authorTibor Frank <tifrank@cisco.com>2018-09-04 09:37:39 +0200
committerTibor Frank <tifrank@cisco.com>2018-09-07 08:14:33 +0000
commit344ea908c94faf37a10f23627b2f5656ea3e289b (patch)
tree8528f5f230de0d33e966a5474d9f830a223e1f63 /docs/cpta/introduction
parent084295259c8c400068b12add325830388fffe0ba (diff)
CSIT-1262: Add 2n/3n-skx to trending
CSIT-1263: Edit Trending static content Change-Id: Ief60f3bea75fb9fd153f7abb0a5933f1a3e317aa Signed-off-by: Tibor Frank <tifrank@cisco.com>
Diffstat (limited to 'docs/cpta/introduction')
-rw-r--r--docs/cpta/introduction/dashboard.rst68
-rw-r--r--docs/cpta/introduction/failures.rst17
-rw-r--r--docs/cpta/introduction/index.rst54
-rw-r--r--docs/cpta/introduction/introduction.rst24
4 files changed, 107 insertions, 56 deletions
diff --git a/docs/cpta/introduction/dashboard.rst b/docs/cpta/introduction/dashboard.rst
new file mode 100644
index 0000000000..e1922daf82
--- /dev/null
+++ b/docs/cpta/introduction/dashboard.rst
@@ -0,0 +1,68 @@
+Data Plane Performance
+======================
+
+Legend to the tables:
+
+ - **Test Case**: name of FD.io CSIT test case, naming convention
+ `here <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
+ - **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.
+
+3n-hsw
+------
+
+VPP worker on 1t1c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-1t1c-3n-hsw.rst
+
+VPP worker on 2t2c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-2t2c-3n-hsw.rst
+
+VPP worker on 4t4c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-4t4c-3n-hsw.rst
+
+3n-skx
+------
+
+VPP worker on 1t1c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-2t1c-3n-skx.rst
+
+VPP worker on 2t2c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-4t2c-3n-skx.rst
+
+VPP worker on 4t4c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-8t4c-3n-skx.rst
+
+2n-skx
+------
+
+VPP worker on 1t1c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-2t1c-2n-skx.rst
+
+VPP worker on 2t2c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-4t2c-2n-skx.rst
+
+VPP worker on 4t4c
+``````````````````
+
+.. include:: ../../../_build/_static/vpp/performance-trending-dashboard-8t4c-2n-skx.rst
diff --git a/docs/cpta/introduction/failures.rst b/docs/cpta/introduction/failures.rst
index c1811685f9..61e05e987f 100644
--- a/docs/cpta/introduction/failures.rst
+++ b/docs/cpta/introduction/failures.rst
@@ -4,7 +4,7 @@ Failed Tests
The table lists the tests which failed over the <N=14> runs of the trending
jobs.
-Legend to the table:
+Legend to the tables:
- **Test Case**: name of FD.io CSIT test case, naming convention
`here <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
@@ -13,4 +13,17 @@ Legend to the table:
- **Last Failure [VPP-Build-Id]**: VPP build as of last failure.
- **Last Failure [CSIT-Job-Build-Id]**: CSIT build as of last failure.
-.. include:: ../../../_build/_static/vpp/failed-tests.rst
+3n-hsw
+------
+
+.. include:: ../../../_build/_static/vpp/failed-tests-3n-hsw.rst
+
+3n-skx
+------
+
+.. include:: ../../../_build/_static/vpp/failed-tests-3n-skx.rst
+
+2n-skx
+------
+
+.. include:: ../../../_build/_static/vpp/failed-tests-2n-skx.rst
diff --git a/docs/cpta/introduction/index.rst b/docs/cpta/introduction/index.rst
deleted file mode 100644
index 76aed6bbcd..0000000000
--- a/docs/cpta/introduction/index.rst
+++ /dev/null
@@ -1,54 +0,0 @@
-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 (or DPDK) 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 (and DPDK) 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 an algorithm which divides test runs
-into groups according to minimum description length principle.
-The trend value is the population average of the results within a group.
-
-Legend to the tables:
-
- - **Test Case**: name of FD.io CSIT test case, naming convention
- `here <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
- - **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.
-
-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
diff --git a/docs/cpta/introduction/introduction.rst b/docs/cpta/introduction/introduction.rst
new file mode 100644
index 0000000000..e095d8f18b
--- /dev/null
+++ b/docs/cpta/introduction/introduction.rst
@@ -0,0 +1,24 @@
+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 (or DPDK) 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 (and DPDK) 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 an algorithm which divides test runs
+into groups according to minimum description length principle.
+The trend value is the population average of the results within a group.
+
+Tested VPP worker-thread-core combinations (1t1c, 2t1c, 2t2c, 4t2c, 4t4c, 8t4c)
+are listed in separate tables in section 1.x. Followed by trending methodology
+in section 2. and trending graphs in sections 3.x. Performance test data
+used for trending graphs is provided in sections 4.x.