diff options
author | ahothan <ahothan@cisco.com> | 2017-08-08 16:24:56 -0700 |
---|---|---|
committer | ahothan <ahothan@cisco.com> | 2017-08-08 17:48:09 -0700 |
commit | 0ab04ab7103fc4bfb17042b60c1e005049375cc2 (patch) | |
tree | bee0d88a07889fa57c7f44ca3ce7a839ab05ec53 /nfvbench | |
parent | 2d66234fe3b8b3e104e63218b5120a35ca400ea5 (diff) |
Update doc with ndr/pdr section, update config comment
Change-Id: I2e0a771b21371f45fd592ff41dc8f66c0aaeb7e0
Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'nfvbench')
-rw-r--r-- | nfvbench/cfg.default.yaml | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/nfvbench/cfg.default.yaml b/nfvbench/cfg.default.yaml index 8766d53..a462383 100644 --- a/nfvbench/cfg.default.yaml +++ b/nfvbench/cfg.default.yaml @@ -330,7 +330,7 @@ duration_sec: 60 # Can be overridden by --interval interval_sec: 10 -# NDR / PDR configuration ZZ +# NDR / PDR configuration measurement: # Drop rates represent the ratio of dropped packet to the total number of packets sent. # Values provided here are percentages. A value of 0.01 means that at most 0.01% of all @@ -340,8 +340,13 @@ measurement: NDR: 0.001 # Partial Drop Rate in percentage; NDR should always be less than PDR PDR: 0.1 - # The accuracy of NDR and PDR load percentiles; The actual load percentile that match NDR - # or PDR should be within `load_epsilon` difference than the one calculated. + # The accuracy of NDR and PDR as a percnetage of line rate; The exact NDR + # or PDR should be within `load_epsilon` line rate % from the one calculated. + # For example, with a value 0.1, and a line rate of 10Gbps, the accuracy + # of NDR and PDR will be within 0.1% Of 10Gbps or 10Kbps. + # The lower the value the more iterations and the longer it will take to find the NDR/PDR. + # In practice, due to the precision of the traffic generator it is not recommended to + # set it to lower than 0.1 load_epsilon: 0.1 # Location where to store results in a JSON format. Must be container specific path. |