diff options
| author |   ahothan <ahothan@cisco.com> | 2017-12-21 17:17:46 -0800 |
|---|---|---|
| committer | ahothan <ahothan@cisco.com> | 2017-12-21 17:17:46 -0800 |
| commit | efc678c9d3843dcfd373b5749a88c51228b0b27c (patch) | |
| tree | 9eb405d22720aa4332de10a525cfe10c1124724d /docs | |
| parent | a3c54b7fdce6084d6f64aa3cc23740381286a8ff (diff) | |
[NFVBENCH-59] Add Unit Testing of the NDR/PDR convergence algorithm using the dummy traffic gen
[NFVBENCH-60] Fix pylint warnings
Change-Id: I72deec060bf25774d1be33eaeefc74b42a576483
Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/development/design/ndrpdr.rst | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/development/design/ndrpdr.rst b/docs/development/design/ndrpdr.rst index 4f611a0..5361174 100644 --- a/docs/development/design/ndrpdr.rst +++ b/docs/development/design/ndrpdr.rst @@ -28,7 +28,17 @@ The default value of 0.1 indicates for example that the measured NDR and PDR are actual NDR/PDR (e.g. 0.1% of 10Gbps is 10Mbps). It also determines how small the search range must be in the binary search. The recursion narrows down the range by half and stops when: + - the range is smaller than the configured load_epsilon value - or when the search hits 100% or 0% of line rate +One particularity of using a software traffic generator is that the requested Tx rate may not always be met due to +resource limitations (e.g. CPU is not fast enough to generate a very high load). The algorithm should take this into +consideration: + +- always monitor the actual Tx rate achieved +- actual Tx rate is always <= requested Tx rate +- the measured drop rate should always be relative to the actual Tx rate +- if the actual Tx rate is < requested Tx rate and the measured drop rate is already within threshold (<NDR/PDR threshold) then the binary search must stop with proper warning + |