aboutsummaryrefslogtreecommitdiffstats
path: root/docs/cpta/introduction/index.rst
diff options
context:
space:
mode:
authorMaciek Konstantynowicz <mkonstan@cisco.com>2018-04-28 12:50:59 +0100
committerMaciek Konstantynowicz <mkonstan@cisco.com>2018-04-28 14:11:43 +0100
commit1a72adeb35bfd540f882a107ed1007e4a8545dec (patch)
treed646c3b43f8d331cd72009633d30b65946f5dee6 /docs/cpta/introduction/index.rst
parent9eb9f9300831fcdd56dbefac7aaec5659cdfc31c (diff)
More edits in trending docs: methodology, dashboard.
Change-Id: I008fd39c57810dcf4cb84e5a9fc4f9adf6923a4f Signed-off-by: Maciek Konstantynowicz <mkonstan@cisco.com>
Diffstat (limited to 'docs/cpta/introduction/index.rst')
-rw-r--r--docs/cpta/introduction/index.rst37
1 files changed, 20 insertions, 17 deletions
diff --git a/docs/cpta/introduction/index.rst b/docs/cpta/introduction/index.rst
index 8b3c17029d..c724c30bad 100644
--- a/docs/cpta/introduction/index.rst
+++ b/docs/cpta/introduction/index.rst
@@ -4,18 +4,28 @@ VPP Performance Dashboard
Description
-----------
-Dashboard tables list a summary of latest per test-case VPP Maximum
-Receive Rate (MRR) performance trend, trend compliance metrics and
-detected number of anomalies. Data samples come from the CSIT VPP
-performance trending jobs executed twice a day, every 12 hrs (02:00,
-14:00 UTC). All trend and anomaly evaluation is based on a rolling
-window of <N=14> data samples, covering last 7 days.
+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 <N=14> data
+samples, covering last 7 days.
Legend to table:
- - **Test Case** : name of CSIT test case, naming convention in
- `CSIT wiki <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
- - **Trend [Mpps]** : last value of trend.
+ - **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.
@@ -24,17 +34,10 @@ Legend to table:
- **Progressions [#]** : Number of progressions detected.
- **Outliers [#]** : Number of outliers detected.
-MRR tests measure the packet forwarding rate under the maximum load
-offered by traffic generator over a set trial duration, regardless of
-packet loss.
-
-For more detail about MRR tests, trend and anomaly calculations please
-refer to :ref:`trending_methodology` section.
-
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 daily trending graphs in sections 3.x. Daily trending
-data used is provided in sections 4.x.
+data used for graphs is provided in sections 4.x.
VPP worker on 1t1c
------------------