X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Fmethodology_data_plane_throughput%2Fmethodology_data_plane_throughput.rst;h=a26b40088b7f78b8c0ca1118c098c036fcdeb1fa;hb=38c3ff73f5cbc0124782c7c7d235ba36f57872ae;hp=762a7c26751aa55ab6bf0bfb15dfe5badea0e3a0;hpb=342ba492f7066402e35654199193e20135f39b6d;p=csit.git

diff --git a/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst b/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
index 762a7c2675..a26b40088b 100644
--- a/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
+++ b/docs/report/introduction/methodology_data_plane_throughput/methodology_data_plane_throughput.rst
@@ -1,3 +1,5 @@
+.. _data_plane_throughput:
+
 Data Plane Throughput Tests
 ---------------------------
 
@@ -11,6 +13,10 @@ Following throughput test methods are used:
 - MRR - Maximum Receive Rate
 - PLRsearch - Probabilistic Loss Ratio search
 
+..
+    TODO: Add RECONF.
+    TODO: Link to method-specific pages instead of duplicate info below.
+
 Description of each test method is followed by generic test properties
 shared by all methods.
 
@@ -22,10 +28,10 @@ Description
 
 Multiple Loss Ratio search (MLRsearch) tests discover multiple packet
 throughput rates in a single search, reducing the overall test execution
-time compared to a binary search. Each rate associated with a distinct
-Packet Loss Ratio (PLR) criteria. In FD.io CSIT two throughput rates are
-discovered: Non-Drop Rate (NDR, with zero packet loss, PLR=0) and
-Partial Drop Rate (PDR, with PLR<0.5%). MLRsearch is compliant with
+time compared to a binary search. Each rate is associated with a
+distinct Packet Loss Ratio (PLR) criteria. In FD.io CSIT two throughput
+rates are discovered: Non-Drop Rate (NDR, with zero packet loss, PLR=0)
+and Partial Drop Rate (PDR, with PLR<0.5%). MLRsearch is compliant with
 :rfc:`2544`.
 
 Usage
@@ -47,8 +53,8 @@ Details
 ~~~~~~~
 
 See :ref:`mlrsearch_algorithm` section for more detail. MLRsearch is
-being standardized in IETF in `draft-vpolak-mkonstan-mlrsearch
-<https://tools.ietf.org/html/draft-vpolak-mkonstan-bmwg-mlrsearch>`_.
+being standardized in IETF in `draft-ietf-bmwg-mlrsearch
+<https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-mlrsearch-01>`_.
 
 MRR Tests
 ^^^^^^^^^
@@ -65,6 +71,9 @@ offered by traffic generator (dependent on link type and NIC model) over
 a set trial duration, regardless of packet loss. Maximum load for
 specified Ethernet frame size is set to the bi-directional link rate.
 
+Usage
+~~~~~
+
 MRR tests are much faster than MLRsearch as they rely on a single trial
 or a small set of trials with very short duration. It is this property
 that makes them suitable for continuous execution in daily performance
@@ -72,7 +81,7 @@ trending jobs enabling detection of performance anomalies (regressions,
 progressions) resulting from data plane code changes.
 
 MRR tests are also used for VPP per patch performance jobs verifying
-patch performance vs. parent. CSIT reports include MRR throughput
+patch performance vs parent. CSIT reports include MRR throughput
 comparisons between releases and test environments. Small frame sizes
 only (64b/78B, IMIX).
 
@@ -84,9 +93,9 @@ configuration.
 
 FD.io CSIT performance dashboard includes complete description of
 `daily performance trending tests
-<https://docs.fd.io/csit/master/trending/methodology/performance_tests.html>`_
+<https://s3-docs.fd.io/csit/master/trending/methodology/performance_tests.html>`_
 and `VPP per patch tests
-<https://docs.fd.io/csit/master/trending/methodology/perpatch_performance_tests.html>`_.
+<https://s3-docs.fd.io/csit/master/trending/methodology/perpatch_performance_tests.html>`_.
 
 PLRsearch Tests
 ^^^^^^^^^^^^^^^
@@ -108,13 +117,13 @@ PLRsearch are run to discover a sustained throughput for PLR=10^-7
 frame sizes (64b/78B) are presented in packet throughput graphs (Box
 Plots) for a small subset of baseline tests.
 
-Each soak test lasts 2hrs and is executed at least twice. Results are
+Each soak test lasts 30 minutes and is executed at least twice. Results are
 compared against NDR and PDR rates discovered with MLRsearch.
 
 Details
 ~~~~~~~
 
-See :ref:`plrsearch_algorithm` section for more detail. PLRsearch is
+See :ref:`plrsearch` methodology section for more detail. PLRsearch is
 being standardized in IETF in `draft-vpolak-bmwg-plrsearch
 <https://tools.ietf.org/html/draft-vpolak-bmwg-plrsearch>`_.
 
@@ -135,3 +144,8 @@ properties:
 - All measured and reported packet and bandwidth rates are aggregate
   bi-directional rates reported from external Traffic Generator
   perspective.
+
+..
+    TODO: Incorporate ASTF specifics: No IMIX, transactions instead of packets,
+    slightly non-symmetric traffic with TCP profiles, unsure max_rate.
+    TODO: Mention latency.