6 .. _vpp_test_environment:
11 In order to determine any benchmark anomalies (progressions,
12 regressions) between releases of a specific data-plane DUT application
13 (e.g. VPP, DPDK), the DUT needs to be tested in the same test
14 environment, to avoid test environment changes impacting the results and
17 In order to enable test system evolution, a mirror scheme is required to
18 determine benchmarking anomalies between releases of specific test
19 system like CSIT. This is achieved by testing the same DUT application
20 version between releases of CSIT test system.
22 CSIT test environment versioning scheme ensures integrity of all the
23 test system components, including their HW revisions, compiled SW code
24 versions and SW source code, within a specific CSIT version. Components
25 included in the CSIT environment versioning include:
27 - Server hosts hardware firmware and BIOS (motherboard, processsor, NIC(s), accelerator card(s)).
28 - Server host Linux operating system versions.
29 - Server host Linux configuration.
30 - TRex Traffic Generator version, drivers and configuration.
31 - CSIT framework code.
33 Following is the list of CSIT versions to date:
35 - Ver. 1 associated with CSIT rls1908 git branch as of 2019-08-21.
36 - Ver. 2 associated with CSIT rls2001 git branch as of 2020-03-27.
37 - Ver. 3 interim associated with master branch as of 2020-xx-xx.
38 - Ver. 4 associated with CSIT rls2005 git branch as of 2020-06-24.
40 To identify performance changes due to VPP code changes from v20.01.0 to
41 v20.05.0, both have been tested in CSIT environment ver. 4 and compared
42 against each other. All substantial progressions has been marked up with
43 RCA analysis. See Current vs Previous Release and Known Issues.
45 CSIT environment ver. 4 has been evaluated against the ver. 2 by
46 benchmarking VPP v20.01.0 in both environrment versions.
48 .. include:: ../introduction/test_environment_intro.rst
50 .. include:: ../introduction/test_environment_sut_conf_1.rst
61 VPP Compile Parameters
62 ~~~~~~~~~~~~~~~~~~~~~~
64 `FD.io VPP compile job`_
66 VPP Install Parameters
67 ~~~~~~~~~~~~~~~~~~~~~~
71 $ dpkg -i --force-all *vpp*
73 VPP Startup Configuration
74 ~~~~~~~~~~~~~~~~~~~~~~~~~
76 VPP startup configuration vary per test case, with different settings
77 for `$$CORELIST_WORKERS`, `$$NUM_RX_QUEUES`, `$$UIO_DRIVER`, and
78 `$$NO_MULTI_SEG` parameter. List of plugins to enable is driven by test
79 requirements. Default template is provided below:
94 cli-listen /run/vpp/cli.sock
100 socket-name /run/vpp/api.sock
114 plugin <$$test_requirement>_plugin.so
121 corelist-workers $$CORELIST_WORKERS
126 buffers-per-numa 215040
129 # Below: in case of dpdk based drivers (vfio-pci) only
132 uio-driver $$UIO_DRIVER
137 num-rx-queues $$NUM_RX_QUEUES
139 no-tx-checksum-offload
144 Description of VPP startup settings used in CSIT is provided in
145 :ref:`test_methodology`.
147 .. include:: ../introduction/test_environment_tg.rst
149 .. include:: ../introduction/test_environment_pre_test_server_calib.rst
151 .. include:: ../introduction/test_environment_sut_calib_skx.rst
153 .. include:: ../introduction/test_environment_sut_calib_clx.rst
155 .. include:: ../introduction/test_environment_sut_calib_hsw.rst
157 .. include:: ../introduction/test_environment_sut_calib_dnv.rst
159 .. include:: ../introduction/test_environment_sut_calib_tsh.rst