X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Fvpp_performance_tests%2Fthroughput_speedup_multi_core%2Findex.rst;h=b3504010f31033e5788fa5cc2febec2320eb7ec9;hp=feb6e78c0467752e698a8d668bd7d6aac23a31aa;hb=e0e76e6ac30312d84424023a76d612606e0040d4;hpb=8243ea78854683f2f80da53d8f197f10316e4801 diff --git a/docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst b/docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst index feb6e78c04..b3504010f3 100644 --- a/docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst +++ b/docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst @@ -1,9 +1,10 @@ -.. _throughput_speedup_multi_core: .. raw:: latex \clearpage +.. _throughput_speedup_multi_core: + Speedup Multi-Core ================== @@ -13,6 +14,25 @@ LF FD.io labs: 3n-hsw, 2n-skx, 2n-skx. Grouped bars illustrate the 64B/78B packet throughput speedup ratio for 2- and 4-core multi- threaded VPP configurations relative to 1-core configurations. +Additional information about graph data: + +#. **Graph Title**: describes tested packet path, testbed topology, + processor model, NIC model, packet size used by data plane workers and + indication of VPP DUT configuration. + +#. **X-axis Labels**: number of cores. + +#. **Y-axis Labels**: measured Packets Per Second [pps] throughput + values. + +#. **Graph Legend**: lists CSIT test suites executed to generate graphed test + results. + +#. **Hover Information**: lists number of runs executed, specific test + substring, mean value of the measured packet throughput, calculated perfect + throughput value, difference between measured and perfect values and + relative speedup value. + .. note:: Test results have been generated by @@ -22,10 +42,7 @@ threaded VPP configurations relative to 1-core configurations. result files csit-vpp-perf-|srelease|-\*.zip `archived here <../../_static/archive/>`_. Required per test case data set size is **10**, but for VPP tests - the actual size varies per test case and is <=10. This is due to - not all test executions completing successfully due to a known - `VPP-1361 `_ issue - sporadically impacting physical interface up/down state. + the actual size varies per test case and is <=10. .. toctree:: :maxdepth: 3