NameDateSize

..13-Mar-20184 KiB

__init__.pyH A D13-Mar-20180

config/H13-Mar-2018118

graph_template.htmlH A D13-Mar-20183 KiB

h_avc.pyH A D13-Mar-20185.4 KiB

phantom/H13-Mar-201843

readme.txtH A D13-Mar-2018917

regression/H13-Mar-20184 KiB

report_template.htmlH A D13-Mar-20181.4 KiB

sshpass.expH A D13-Mar-2018338

trex_control_plane/H13-Mar-2018155

trex_perf.pyH A D13-Mar-201843.3 KiB

wkhtmltopdf-amd64H A D13-Mar-20187.9 MiB

readme.txt

1README - trex_perf.py
2=====================
3
4This script uses the TRex RESTfull client-server conrtol plane achitecture and tries to find the maximum M (platform factor) for trex before hitting one of two stopping conditions:
5(*) Packet drops
6(*) High latency.
7    Since high latency can change from one platform to another, and might suffer from kickoff peak (espicially at VM), it is the user responsibility to provide the latency condition. 
8    A common value used by non-vm machines is 1000, where in VM machines values around 5000 are more common.
9
10please note that '-f' and '-c' options are mandatory. 
11
12Also, this is the user's responsibility to make sure a TRex is running, listening to relevant client request coming from this script.
13
14example for finding max M (between 10 to 100) with imix_fast_1g.yaml traffic profile:
15./trex_perf.py -m 10 100 -c config/trex-hhaim.cfg all drop -f cap2/imix_fast_1g.yaml
16