diff options
| author |   Hanoh Haim <hhaim@cisco.com> | 2017-01-15 11:02:36 +0200 |
|---|---|---|
| committer | Hanoh Haim <hhaim@cisco.com> | 2017-01-15 11:02:36 +0200 |
| commit | 4e5a651c8e052cdbcad73f6af5ce065ffd6dbce4 (patch) | |
| tree | b5d95544c6b9401b7e6f933e656a781b29cce7a8 | |
| parent | 734ce41c65a49b0a74b515c7d9c6a2b888bbddb9 (diff) | |
minor update doc
Signed-off-by: Hanoh Haim <hhaim@cisco.com>
| -rwxr-xr-x | doc/trex_analytics.asciidoc | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/trex_analytics.asciidoc b/doc/trex_analytics.asciidoc index b9dbf4c6..a5b223ea 100755 --- a/doc/trex_analytics.asciidoc +++ b/doc/trex_analytics.asciidoc @@ -22,11 +22,14 @@ endif::backend-xhtml11[] = TRex performance trend -Performance is measured in a metric called MPPS/Core (Norm), which stands for Mega-Packet per second (Norm). + + +This document tracks the performance of TRex Stateless use-cases of various hardware and NICS. +The intention is to track the TRex software performance and not the NIC driver performance, however from this document you can learn the difference between different driver implementation (cycles/packets) +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. + +We measure the MPPS of the DUT in its 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) + + |