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=06efbc2798785263e879190e8e6112fd9e947641;hb=refs%2Fchanges%2F05%2F34005%2F1;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..06efbc2798 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,9 @@ Following throughput test methods are used: - MRR - Maximum Receive Rate - PLRsearch - Probabilistic Loss Ratio search +.. + TODO: Add RECONF. + Description of each test method is followed by generic test properties shared by all methods. @@ -22,10 +27,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 +52,8 @@ Details ~~~~~~~ See :ref:`mlrsearch_algorithm` section for more detail. MLRsearch is -being standardized in IETF in `draft-vpolak-mkonstan-mlrsearch -`_. +being standardized in IETF in `draft-ietf-bmwg-mlrsearch +`_. MRR Tests ^^^^^^^^^ @@ -65,6 +70,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 +80,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 +92,9 @@ configuration. FD.io CSIT performance dashboard includes complete description of `daily performance trending tests -`_ +`_ and `VPP per patch tests -`_. +`_. PLRsearch Tests ^^^^^^^^^^^^^^^ @@ -108,13 +116,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 `_.