aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/trex_performance_tests/throughput_trending.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/report/trex_performance_tests/throughput_trending.rst')
-rw-r--r--docs/report/trex_performance_tests/throughput_trending.rst6
1 files changed, 4 insertions, 2 deletions
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.