diff options
| author |   itraviv <itraviv@cisco.com> | 2017-01-12 15:45:35 +0200 |
|---|---|---|
| committer | itraviv <itraviv@cisco.com> | 2017-01-12 15:45:58 +0200 |
| commit | 6cdb4a984508a27a94df24ba9dabf050f3c319fd (patch) | |
| tree | ab989d0d0f72dd29f28e053246d233c8e3be2df9 /doc/trex_analytics.asciidoc | |
| parent | 32366ab4524073ab59e59fc9895b0b2d5a73b438 (diff) | |
added option to support input from elk in analyticsWebReport, added TRexDataAnalysisV2 that has OOP design, added details to asciidoc that provide more info on how we calculate MPPS/Core
Signed-off-by: itraviv <itraviv@cisco.com>
Diffstat (limited to 'doc/trex_analytics.asciidoc')
| -rwxr-xr-x | doc/trex_analytics.asciidoc | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/trex_analytics.asciidoc b/doc/trex_analytics.asciidoc index 10681925..b9dbf4c6 100755 --- a/doc/trex_analytics.asciidoc +++ b/doc/trex_analytics.asciidoc @@ -22,6 +22,19 @@ endif::backend-xhtml11[] = TRex performance trend +Performance is measured in a metric called MPPS/Core (Norm), which stands for Mega-Packet per second (Norm). + + + +How the calculation is made? + + + +We measure the MPPS of the dut in it's best working point. + +The measurement is then scaled to fit 100% CPU utilization, and finally divided by the number of cores the device has, +to get a normalized MPPS/Core which is denoted as MPPS/Core (Norm) + + + +How to run these tests? + +[source,python] +---- + trex-core/scripts> ./run_regression --stl -t <name of test> --cfg setups/<name of setup> +---- == Setup: XL710 (4x40GbE) trex-08 |