7 `TRex traffic generator <https://wiki.fd.io/view/TRex>`_ is used for all
8 CSIT performance tests. TRex stateless mode is used to measure NDR and
9 PDR throughputs using binary search (NDR and PDR discovery tests) and
10 for quick checks of DUT performance against the reference NDRs (NDR
11 check tests) for specific configuration.
13 TRex is installed and run on the TG compute node. The typical procedure
16 - If the TRex is not already installed on TG, it is installed in the
17 suite setup phase - see `TRex intallation`_.
18 - TRex configuration is set in its configuration file
23 - TRex is started in the background mode
26 $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /tmp/trex.log 2>&1 &' > /dev/null
28 - There are traffic streams dynamically prepared for each test, based on traffic
29 profiles. The traffic is sent and the statistics obtained using
30 :command:`trex_stl_lib.api.STLClient`.
35 Following sequence is followed to measure packet loss:
37 - Create an instance of STLClient.
38 - Connect to the client.
41 - Send the traffic for defined time.
44 If there is a warm-up phase required, the traffic is sent also before
45 test and the statistics are ignored.
50 If measurement of latency is requested, two more packet streams are
51 created (one for each direction) with TRex flow_stats parameter set to
52 STLFlowLatencyStats. In that case, returned statistics will also include
53 min/avg/max latency values.