CSIT 1701 report files and script

[csit.git] / docs / report / vpp_performance_tests_hw / packet_latency_graphs / ipv4.rst

diff --git a/docs/report/vpp_performance_tests_hw/packet_latency_graphs/ipv4.rst b/docs/report/vpp_performance_tests_hw/packet_latency_graphs/ipv4.rst
new file mode 100644 (file)
index 0000000..84fc827
--- /dev/null
+++ b/docs/report/vpp_performance_tests_hw/packet_latency_graphs/ipv4.rst
@@ -0,0 +1,99 @@
+IPv4 Routed-Forwarding\r
+======================\r
+\r
+This section provides a summary of VPP Phy-to-Phy IPv4 Routed-Forwarding\r
+performance illustrating packet latency measured at 50% of discovered NDR\r
+throughput rate. Latency is reported for VPP running in multiple\r
+configurations of VPP worker thread(s), a.k.a. VPP data plane thread (s), and\r
+their physical CPU core(s) placement.\r
+\r
+Title of each graph is a regex (regular expression) matching all plotted\r
+test case throughput measurements.\r
+\r
+.. note::\r
+\r
+    Data sources for reported test results: i) FD.io test executor jobs\r
+    `csit-vpp-perf-1701-all <https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1701-all/>`_\r
+    and\r
+    `csit-vpp-perf-1701-long <https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1701-long/>`_\r
+    , ii) archived FD.io jobs test result output files\r
+    `csit-vpp-perf-1701-all#job-number <https://nexus.fd.io/link>`_.\r
+\r
+VPP packet latency - running in configuration of **one worker thread (1t) on one\r
+physical core (1c)** - is presented in the figure below.\r
+\r
+.. raw:: html\r
+\r
+    <iframe width="700" height="700" frameborder="0" scrolling="no" src="../../_static/vpp/64B-1t1c-ethip4-ip4-ndrdisc-lat50.html"></iframe>\r
+\r
+*Figure 1. VPP 1thread 1core - packet latency for Phy-to-Phy IPv4 Routed-Forwarding.*\r
+\r
+CSIT test cases used to generate results presented above can be found in CSIT\r
+git repository by filtering with specified regex as follows:\r
+\r
+.. code-block:: bash\r
+\r
+    $ csit/tests/perf\r
+    $ grep -E "64B-1t1c-ethip4-ip4[a-z0-9]+-[a-z-]*ndrdisc" *\r
+\r
+    10ge2p1x520-ethip4-ip4base-copwhtlistbase-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4base-copwhtlistbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-iacldstbase-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4base-iacldstbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ipolicemarkbase-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4base-ipolicemarkbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4base-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale200k-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4scale200k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale20k-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4scale20k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale2m-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4scale2m-ndrdisc\r
+    40ge2p1xl710-ethip4-ip4base-ndrdisc.robot:| tc01-64B-1t1c-ethip4-ip4base-ndrdisc\r
+\r
+VPP packet latency - running in configuration of **two worker threads (2t) on two\r
+physical cores (2c)** - is presented in the figure below.\r
+\r
+.. raw:: html\r
+\r
+    <iframe width="700" height="700" frameborder="0" scrolling="no" src="../../_static/vpp/64B-2t2c-ethip4-ip4-ndrdisc-lat50.html"></iframe>\r
+\r
+*Figure 2. VPP 2threads 2cores - packet latency for Phy-to-Phy IPv4 Routed-Forwarding.*\r
+\r
+CSIT test cases used to generate results presented above can be found in CSIT\r
+git repository by filtering with specified regex as follows:\r
+\r
+.. code-block:: bash\r
+\r
+    $ csit/tests/perf\r
+    $ grep -E "64B-2t2c-ethip4-ip4[a-z0-9]+-[a-z-]*ndrdisc" *\r
+\r
+    10ge2p1x520-ethip4-ip4base-copwhtlistbase-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4base-copwhtlistbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-iacldstbase-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4base-iacldstbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ipolicemarkbase-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4base-ipolicemarkbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4base-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale200k-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4scale200k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale20k-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4scale20k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale2m-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4scale2m-ndrdisc\r
+    40ge2p1xl710-ethip4-ip4base-ndrdisc.robot:| tc07-64B-2t2c-ethip4-ip4base-ndrdisc\r
+\r
+VPP packet latency - running in configuration of **four worker threads (4t) on four\r
+physical cores (4c)** - is presented in the figure below.\r
+\r
+.. raw:: html\r
+\r
+    <iframe width="700" height="700" frameborder="0" scrolling="no" src="../../_static/vpp/64B-4t4c-ethip4-ip4-ndrdisc-lat50.html"></iframe>\r
+\r
+*Figure 3. VPP 4threads 4cores - packet latency for Phy-to-Phy IPv4 Routed-Forwarding.*\r
+\r
+CSIT test cases used to generate results presented above can be found in CSIT\r
+git repository by filtering with specified regex as follows:\r
+\r
+.. code-block:: bash\r
+\r
+    $ csit/tests/perf\r
+    $ grep -E "64B-4t4c-ethip4-ip4[a-z0-9]+-[a-z-]*ndrdisc" *\r
+\r
+    10ge2p1x520-ethip4-ip4base-copwhtlistbase-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4base-copwhtlistbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-iacldstbase-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4base-iacldstbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ipolicemarkbase-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4base-ipolicemarkbase-ndrdisc\r
+    10ge2p1x520-ethip4-ip4base-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4base-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale200k-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4scale200k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale20k-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4scale20k-ndrdisc\r
+    10ge2p1x520-ethip4-ip4scale2m-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4scale2m-ndrdisc\r
+    40ge2p1xl710-ethip4-ip4base-ndrdisc.robot:| tc13-64B-4t4c-ethip4-ip4base-ndrdisc\r
+\r