X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Ftrex_performance_tests%2Fthroughput_trending.rst;fp=docs%2Freport%2Ftrex_performance_tests%2Fthroughput_trending.rst;h=9106cb4bdfac8ad88e75b6a731a86d950b785789;hp=cb2751972f405d362bfdb69015e3d80fcabf296e;hb=fdf6fb175c4a8051ff75732b8b1bae139bacf9c8;hpb=37eba068fba30ebecadb8ea175273d057fcb6105

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.