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