aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report
diff options
context:
space:
mode:
authorVratko Polak <vrpolak@cisco.com>2018-05-28 11:53:45 +0200
committerVratko Polak <vrpolak@cisco.com>2018-06-18 12:20:18 +0200
commita9f251c649a5dea7428a43dc24380077a72dacba (patch)
treee56e2cae2970968efe5f5ca285feb9f3b8ce2bbc /docs/report
parent938a0c9cec6d2177e098653ad398372fb482c36f (diff)
CSIT-986: Implement proposed MDR improvements
+ Use first intermediate with goal in initial phase. + Measure above MRR if that got zero loss. + Always prioritizes NDR in internal search. + Rename classes. + Copy code for standalone PyPI publishing. - Original files will be deleted after publish. Change-Id: I5169d602d1e5e35a1894645cd52e70d791871608 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'docs/report')
-rw-r--r--docs/report/vpp_performance_tests/mdr_search.rst19
1 files changed, 12 insertions, 7 deletions
diff --git a/docs/report/vpp_performance_tests/mdr_search.rst b/docs/report/vpp_performance_tests/mdr_search.rst
index e2d0065d92..f47c0f5111 100644
--- a/docs/report/vpp_performance_tests/mdr_search.rst
+++ b/docs/report/vpp_performance_tests/mdr_search.rst
@@ -215,12 +215,14 @@ Non-initial phases
transmit rate had the loss lower or equal to PLR, then
the new transmit rate is PDR upper_bound
increased by two PDR interval widths.
- - Else, *if* NDR (or PDR) interval does not meet the current phase width goal,
- prepare for internal search. The new transmit rate is
- (lower bound + upper bound) / 2.
- It does not matter much which interval is investigated first.
- The current implementation starts with NDR, unless PDR interval is wider
- (but always preferring NDR is slightly better).
+ - If interval width is higher than the current phase goal:
+
+ - Else, *if* NDR interval does not meet the current phase width goal,
+ prepare for internal search. The new transmit rate is
+ (NDR lower bound + NDR upper bound) / 2.
+ - Else, *if* PDR interval does not meet the current phase width goal,
+ prepare for internal search. The new transmit rate is
+ (PDR lower bound + PDR upper bound) / 2.
- Else, *if* some bound has still only been measured at a lower duration,
prepare to re-measure at the current duration (and the same transmit rate).
The order of priorities is:
@@ -264,7 +266,7 @@ but without detailing their mutual interaction.
Narrow intervals make external search take more time to find a valid bound.
If the new transmit increased or decreased rate would result in width
less than the current goal, increase/decrease more.
- This can happen if measurement for the other interval
+ This can happen if the measurement for the other interval
makes the current interval too narrow.
Similarly, take care the measurements in the initial phase
create wide enough interval.
@@ -315,6 +317,9 @@ Data in tables is based on result of 6 runs.
Tables
``````
+.. note:: The comparison was done for the MDR code
+ before https://gerrit.fd.io/r/12761
+
.. table:: Table 1. Search part of test duration.
==================== ========== =========== =========== ========== =========== ===========