diff options
Diffstat (limited to 'docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst')
| -rw-r--r-- | docs/report/vpp_performance_tests/throughput_speedup_multi_core/index.rst | 17 |
1 files changed, 10 insertions, 7 deletions
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 b3f95ec6c3..4f3acaa0c5 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 @@ -7,10 +7,10 @@ Speedup Multi-Core ================== -Throughput Speedup Multi-Core graphs are generated based on results from -multiple executions of the same CSIT performance tests across the three -physical testbeds within LF FD.io labs. Plotted grouped bars illustrate -the 64B/78B packet throughput speedup ratio for 2- and 4-core multi- +Speedup Multi-Core throughput graphs are generated by multiple +executions of the same performance tests across physical testbeds hosted +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. .. note:: @@ -18,11 +18,14 @@ threaded VPP configurations relative to 1-core configurations. Test results have been generated by `FD.io test executor vpp performance job 3n-hsw`_, `FD.io test executor vpp performance job 3n-skx`_ and - `FD.io test executor vpp performance job 2n-skx`_ with Robot Framework + `FD.io test executor vpp performance job 2n-skx`_ with RF result files csit-vpp-perf-|srelease|-\*.zip `archived here <../../_static/archive/>`_. - Plotted data set size per test case is equal to the number of job executions - presented in this report version: **10**. + 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 <https://jira.fd.io/browse/VPP-1361>`_ issue + sporadically impacting physical interface up/down state. .. toctree:: :maxdepth: 1 |