diff options
author | Vratko Polak <vrpolak@cisco.com> | 2021-11-16 17:32:50 +0100 |
---|---|---|
committer | Tibor Frank <tifrank@cisco.com> | 2021-11-18 12:15:38 +0000 |
commit | cc58afc7de521e571fe4cbaa4c9841a2d3e9be52 (patch) | |
tree | ac21a20208b01cb9543ea2476f62aa59c30d0e15 /docs/report/trex_performance_tests | |
parent | 1493f602debb12f1ba152b74c16d1a379a53e50f (diff) |
Report: Improve docs related to TRex
Change-Id: I0ed346ff30c61d28b5a2232ef2f9d32d26c1ae2c
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'docs/report/trex_performance_tests')
-rw-r--r-- | docs/report/trex_performance_tests/overview.rst | 11 | ||||
-rw-r--r-- | docs/report/trex_performance_tests/throughput_trending.rst | 6 |
2 files changed, 10 insertions, 7 deletions
diff --git a/docs/report/trex_performance_tests/overview.rst b/docs/report/trex_performance_tests/overview.rst index 9740179df7..8ad8850ea8 100644 --- a/docs/report/trex_performance_tests/overview.rst +++ b/docs/report/trex_performance_tests/overview.rst @@ -1,14 +1,14 @@ Overview ======== -TREX performance test results are reported for a range of processors. -For description of physical testbeds used for TREX performance tests +TRex performance test results are reported for a range of processors. +For description of physical testbeds used for TRex performance tests please refer to :ref:`tested_physical_topologies`. Logical Topology ---------------- -CSIT TREX performance tests are executed on physical testbeds described +CSIT TRex performance tests are executed on physical testbeds described in :ref:`tested_physical_topologies`. Logical topology use 1 nic that has loopback connected ports. See figure below. @@ -52,11 +52,12 @@ topologies and configurations: - 10% of discovered PDR throughput. - Minimal offered load. -|csit-release| includes following TRex data plane functionality +|csit-release| includes tests using the following TRex traffic profiles +(corresponding to data plane functionality when DUT is used) performance tested across a range of NIC drivers and NIC models: +-----------------------+----------------------------------------------+ -| Functionality | Description | +| Traffic profile | Corresponding dataplane functionality | +=======================+==============================================+ | IPv4 Base | IPv4 routing. | +-----------------------+----------------------------------------------+ diff --git a/docs/report/trex_performance_tests/throughput_trending.rst b/docs/report/trex_performance_tests/throughput_trending.rst index cb2751972f..9106cb4bdf 100644 --- a/docs/report/trex_performance_tests/throughput_trending.rst +++ b/docs/report/trex_performance_tests/throughput_trending.rst @@ -1,12 +1,14 @@ Throughput Trending ------------------- -In addition to reporting throughput comparison between TRex releases, CSIT provides continuous performance trending for master branch: #. `TRex Trending Graphs <https://s3-docs.fd.io/csit/master/trending/ndrpdr_trending/trex.html>`_: per TRex test case throughput trend, trend compliance and summary of - detected anomalies. + detected anomalies. We expect TRex to hit the curently used bps or pps limit, + so no anomalies here (unless we change those limits in CSIT). #. `TRex Latency Graphs <https://s3-docs.fd.io/csit/master/trending/ndrpdr_latency_trending/trex.html>`_: per TRex build NDRPDR latency measurements against the trendline. + We have seen in past that the latency numbers can depend on TRex version, + NIC firmware, or driver used. |