diff options
author | Maciek Konstantynowicz <mkonstan@cisco.com> | 2018-04-29 12:55:59 +0100 |
---|---|---|
committer | Maciek Konstantynowicz <mkonstan@cisco.com> | 2018-04-29 12:55:59 +0100 |
commit | c6aea4422456d455efd0c7ffce94aa0bc0a4dcbf (patch) | |
tree | f1466c4731e1b47b46862ef6fa0b054d6397c6fa /docs/cpta/introduction/index.rst | |
parent | 1a72adeb35bfd540f882a107ed1007e4a8545dec (diff) |
Trending docs: format and section naming fixes.
Change-Id: I891100a7a89bf174df8ac911ba997af8e429a76e
Signed-off-by: Maciek Konstantynowicz <mkonstan@cisco.com>
Diffstat (limited to 'docs/cpta/introduction/index.rst')
-rw-r--r-- | docs/cpta/introduction/index.rst | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/docs/cpta/introduction/index.rst b/docs/cpta/introduction/index.rst index c724c30bad..016037b067 100644 --- a/docs/cpta/introduction/index.rst +++ b/docs/cpta/introduction/index.rst @@ -8,13 +8,12 @@ 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. +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 @@ -36,8 +35,8 @@ Legend to table: 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 for graphs is provided in sections 4.x. +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 ------------------ |