+ - **Description**: MRR tests are complementary to MLRsearch tests,
+ as they provide a maximum “raw” throughput benchmark for
+ development and testing community. MRR tests measure the packet
+ forwarding rate under the maximum load 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 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 comparisons
+ between releases and test environments. Small frame sizes only
+ (64b/78B, IMIX).
+ - **References**: See :ref:`mrr_throughput` for more detailed
+ description of MRR tests configuration used for daily performance
+ trending jobs. VPP per patch test methodology is available on
+ `FD.io CSIT trending pages
+ <https://docs.fd.io/csit/master/trending/methodology/perpatch_performance_tests.html>`_.