Code Review
/
csit.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
review
|
tree
raw
|
inline
| side by side
CSIT-1489: Change graphs to display results by suite generator
[csit.git]
/
docs
/
report
/
vpp_performance_tests
/
overview.rst
diff --git
a/docs/report/vpp_performance_tests/overview.rst
b/docs/report/vpp_performance_tests/overview.rst
index
86116bf
..
3c95919
100644
(file)
--- a/
docs/report/vpp_performance_tests/overview.rst
+++ b/
docs/report/vpp_performance_tests/overview.rst
@@
-1,6
+1,9
@@
Overview
========
Overview
========
+VPP performance test results are reported for all three physical testbed
+types present in FD.io labs: 3-Node Xeon Haswell (3n-hsw), 3-Node Xeon
+Skylake (3n-skx), 2-Node Xeon Skylake (2n-skx) and installed NIC models.
For description of physical testbeds used for VPP performance tests
please refer to :ref:`tested_physical_topologies`.
For description of physical testbeds used for VPP performance tests
please refer to :ref:`tested_physical_topologies`.
@@
-30,9
+33,10
@@
testbeds are shown in figures below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-nic2nic}
- \label{fig:logical-2n-nic2nic}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-2n-nic2nic}
+ \label{fig:logical-2n-nic2nic}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-47,9
+51,10
@@
testbeds are shown in figures below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-nic2nic}
- \label{fig:logical-3n-nic2nic}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-3n-nic2nic}
+ \label{fig:logical-3n-nic2nic}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-107,9
+112,10
@@
SUT running N of VM instances is shown in the figures below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-vm-vhost}
- \label{fig:logical-2n-vm-vhost}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-2n-vm-vhost}
+ \label{fig:logical-2n-vm-vhost}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-124,9
+130,10
@@
SUT running N of VM instances is shown in the figures below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-vm-vhost}
- \label{fig:logical-3n-vm-vhost}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-3n-vm-vhost}
+ \label{fig:logical-3n-vm-vhost}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-187,9
+194,10
@@
below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-container-memif}
- \label{fig:logical-2n-container-memif}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-2n-container-memif}
+ \label{fig:logical-2n-container-memif}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-204,9
+212,10
@@
below.
.. raw:: latex
\begin{figure}[H]
.. raw:: latex
\begin{figure}[H]
- \centering
- \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-container-memif}
- \label{fig:logical-3n-container-memif}
+ \centering
+ \graphicspath{{../_tmp/src/vpp_performance_tests/}}
+ \includegraphics[width=0.90\textwidth]{logical-3n-container-memif}
+ \label{fig:logical-3n-container-memif}
\end{figure}
.. only:: html
\end{figure}
.. only:: html
@@
-259,11
+268,11
@@
topologies and configurations:
regardless of packet loss. Maximum load for specified Ethernet frame
size is set to the bi-directional link rate.
regardless of packet loss. Maximum load for specified Ethernet frame
size is set to the bi-directional link rate.
-|csit-release| includes following
performance test areas covered across
-a range of NIC drivers and NIC models:
+|csit-release| includes following
VPP data plane functionality
+
performance tested across
a range of NIC drivers and NIC models:
+-----------------------+----------------------------------------------+
+-----------------------+----------------------------------------------+
-|
Test Area
| Description |
+|
Functionality
| Description |
+=======================+==============================================+
| ACL | L2 Bridge-Domain switching and |
| | IPv4and IPv6 routing with iACL and oACL IP |
+=======================+==============================================+
| ACL | L2 Bridge-Domain switching and |
| | IPv4and IPv6 routing with iACL and oACL IP |
@@
-337,6
+346,10
@@
a range of NIC drivers and NIC models:
| VPP TCP/IP stack | Tests of VPP TCP/IP stack used with VPP |
| | built-in HTTP server. |
+-----------------------+----------------------------------------------+
| VPP TCP/IP stack | Tests of VPP TCP/IP stack used with VPP |
| | built-in HTTP server. |
+-----------------------+----------------------------------------------+
+| VTS | Virtual Topology System use case tests |
+| | combining VXLAN overlay tunneling with L2BD, |
+| | ACL and KVM VM vhost-user features. |
++-----------------------+----------------------------------------------+
| VXLAN | VXLAN overlay tunnelling integration with |
| | L2XC and L2BD. |
+-----------------------+----------------------------------------------+
| VXLAN | VXLAN overlay tunnelling integration with |
| | L2XC and L2BD. |
+-----------------------+----------------------------------------------+
@@
-350,7
+363,7
@@
Performance Tests Naming
------------------------
FD.io |csit-release| follows a common structured naming convention for
------------------------
FD.io |csit-release| follows a common structured naming convention for
-all performance and system functional tests, introduced in CSIT
rls17
01.
+all performance and system functional tests, introduced in CSIT
-17.
01.
The naming should be intuitive for majority of the tests. Complete
description of FD.io CSIT test naming convention is provided on
The naming should be intuitive for majority of the tests. Complete
description of FD.io CSIT test naming convention is provided on