diff options
| author |   Vratko Polak <vrpolak@cisco.com> | 2019-02-13 09:46:34 +0100 |
|---|---|---|
| committer |   Tibor Frank <tifrank@cisco.com> | 2019-02-13 08:50:07 +0000 |
| commit | 5a57661f740db06903327d29cad02c22ee42665d (patch) | |
| tree | 54016b40e71accf1f4d3dbddff1fb7b0deb0d7cc /docs/report/introduction/methodology_packet_latency.rst | |
| parent | 0a5be92ed271b5bd55871e35a1af4b1f95c97dad (diff) | |
Apply minor improvements to methodology docs
Change-Id: Ice5625c2b04dce174b19748b0ccccdf813b66f2a
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
(cherry picked from commit bbfcee8d3cf51ec01d269245970ef41bb072c580)
Diffstat (limited to 'docs/report/introduction/methodology_packet_latency.rst')
| -rw-r--r-- | docs/report/introduction/methodology_packet_latency.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/report/introduction/methodology_packet_latency.rst b/docs/report/introduction/methodology_packet_latency.rst index 550d12f688..411fe3d6fe 100644 --- a/docs/report/introduction/methodology_packet_latency.rst +++ b/docs/report/introduction/methodology_packet_latency.rst @@ -12,8 +12,8 @@ Reported latency values are measured using following methodology: - TG reports min/avg/max latency values per stream direction, hence two sets of latency values are reported per test case; future release of TRex is expected to report latency percentiles. -- Reported latency values are aggregate across two SUTs due to three - node topology used for all performance tests; for per SUT latency, +- Reported latency values are aggregate across two SUTs if the three + node topology is used for given performance test; for per SUT latency, reported value should be divided by two. - 1usec is the measurement accuracy advertised by TRex TG for the setup used in FD.io labs used by CSIT project. |