6 .. _dpdk_throughput_speedup_multi_core:
11 Speedup Multi-Core throughput graphs are generated by multiple
12 executions of the same performance tests across physical testbeds hosted
13 LF FD.io labs: 2n-skx, 3n-skx, 2n-clx, 3n-tsh, 2n-tx2, 2n-zn2.
14 Grouped bars illustrate the 64B packet throughput speedup ratio for
15 2- and 4-core multi-threaded DPDK configurations relative to 1-core
18 Additional information about graph data:
20 #. **Graph Title**: describes tested packet path, testbed topology,
21 processor model, NIC model, packet size used by data plane workers and
22 indication of VPP DUT configuration.
24 #. **X-axis Labels**: number of cores.
26 #. **Y-axis Labels**: measured Packets Per Second [pps] throughput
29 #. **Graph Legend**: lists CSIT test suites executed to generate graphed test
32 #. **Hover Information**: lists number of runs executed, specific test
33 substring, mean value of the measured packet throughput, calculated perfect
34 throughput value, difference between measured and perfect values and
35 relative speedup value.
39 Test results are stored in
40 `build logs from FD.io dpdk performance job 2n-skx`_,
41 `build logs from FD.io dpdk performance job 3n-skx`_,
42 `build logs from FD.io dpdk performance job 2n-clx`_,
43 `build logs from FD.io dpdk performance job 2n-zn2`_,
44 `build logs from FD.io dpdk performance job 3n-tsh`_,
45 `build logs from FD.io dpdk performance job 2n-tx2`_ with RF
46 result files csit-vpp-perf-|srelease|-\*.zip
47 `archived here <../../_static/archive/>`_.
48 Required per test case data set size is **10**, but for VPP tests
49 the actual size varies per test case and is <=10.