Code Review
/
csit.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
review
|
tree
raw
|
inline
| side by side
Report: Configure rls2302.rc1
[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
a2ead6a
..
bb2ff6c
100644
(file)
--- a/
docs/report/vpp_performance_tests/overview.rst
+++ b/
docs/report/vpp_performance_tests/overview.rst
@@
-1,9
+1,7
@@
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.
+VPP performance test results are reported for a range of processors.
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`.
@@
-260,13
+258,16
@@
topologies and configurations:
- One-Way Packet Latency: measured at different offered packet loads:
- One-Way Packet Latency: measured at different offered packet loads:
- - 100% of discovered NDR throughput.
- - 100% of discovered PDR throughput.
+ - 90% of discovered PDR throughput.
+ - 50% of discovered PDR throughput.
+ - 10% of discovered PDR throughput.
+ - Minimal offered load.
- Maximum Receive Rate (MRR): measure packet forwarding rate under the
maximum load offered by traffic generator over a set trial duration,
regardless of packet loss. Maximum load for specified Ethernet frame
- Maximum Receive Rate (MRR): measure packet forwarding rate under the
maximum load offered by traffic generator over a set trial duration,
regardless of packet loss. Maximum load for specified Ethernet frame
- size is set to the bi-directional link rate.
+ size is set to the bi-directional link rate, unless there is a known
+ limitation preventing Traffic Generator from achieving the line rate.
|csit-release| includes following VPP data plane functionality
performance tested 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:
@@
-278,9
+279,11
@@
performance tested across a range of NIC drivers and NIC models:
| | IPv4and IPv6 routing with iACL and oACL IP |
| | address, MAC address and L4 port security. |
+-----------------------+----------------------------------------------+
| | IPv4and IPv6 routing with iACL and oACL IP |
| | address, MAC address and L4 port security. |
+-----------------------+----------------------------------------------+
-|
COP | IPv4 and IPv6 routing with COP
address |
+|
ADL | IPv4 and IPv6 routing with ADL
address |
| | security. |
+-----------------------+----------------------------------------------+
| | security. |
+-----------------------+----------------------------------------------+
+| GENEVE | GENEVE tunnels for IPv4 routing. |
++-----------------------+----------------------------------------------+
| IPv4 | IPv4 routing. |
+-----------------------+----------------------------------------------+
| IPv6 | IPv6 routing. |
| IPv4 | IPv4 routing. |
+-----------------------+----------------------------------------------+
| IPv6 | IPv6 routing. |
@@
-291,6
+294,10
@@
performance tested across a range of NIC drivers and NIC models:
| IPv6 Scale | IPv6 routing with 20k, 200k and 2M FIB |
| | entries. |
+-----------------------+----------------------------------------------+
| IPv6 Scale | IPv6 routing with 20k, 200k and 2M FIB |
| | entries. |
+-----------------------+----------------------------------------------+
+| IPSecAsyncHW | IPSec encryption with AES-GCM, CBC-SHA-256 |
+| | ciphers in async mode, in combination with |
+| | IPv4 routing. Intel QAT HW acceleration. |
++-----------------------+----------------------------------------------+
| IPSecHW | IPSec encryption with AES-GCM, CBC-SHA-256 |
| | ciphers, in combination with IPv4 routing. |
| | Intel QAT HW acceleration. |
| IPSecHW | IPSec encryption with AES-GCM, CBC-SHA-256 |
| | ciphers, in combination with IPv4 routing. |
| | Intel QAT HW acceleration. |
@@
-302,10
+309,6
@@
performance tested across a range of NIC drivers and NIC models:
| IPSecSW | IPSec encryption with AES-GCM, CBC-SHA-256 |
| | ciphers, in combination with IPv4 routing. |
+-----------------------+----------------------------------------------+
| IPSecSW | IPSec encryption with AES-GCM, CBC-SHA-256 |
| | ciphers, in combination with IPv4 routing. |
+-----------------------+----------------------------------------------+
-| K8s Containers Memif | K8s orchestrated container VPP service chain |
-| | topologies connected over the memif virtual |
-| | interface. |
-+-----------------------+----------------------------------------------+
| KVM VMs vhost-user | Virtual topologies with service |
| | chains of 1 VM using vhost-user |
| | interfaces, with different VPP forwarding |
| KVM VMs vhost-user | Virtual topologies with service |
| | chains of 1 VM using vhost-user |
| | interfaces, with different VPP forwarding |
@@
-334,9
+337,10
@@
performance tested across a range of NIC drivers and NIC models:
| Memif | with different VPP forwarding modes incl. |
| | L2XC, L2BD. |
+-----------------------+----------------------------------------------+
| Memif | with different VPP forwarding modes incl. |
| | L2XC, L2BD. |
+-----------------------+----------------------------------------------+
-| NAT | (Source) Network Address Translation tests |
-| | with varying number of users and ports per |
-| | user. |
+| NAT44 | (Source) Network Address Translation |
+| | deterministic mode and endpoint-dependent |
+| | mode tests with varying number of users and |
+| | ports per user for IPv4. |
+-----------------------+----------------------------------------------+
| QoS Policer | Ingress packet rate measuring, marking and |
| | limiting (IPv4). |
+-----------------------+----------------------------------------------+
| QoS Policer | Ingress packet rate measuring, marking and |
| | limiting (IPv4). |
@@
-363,7
+367,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-17.01
.
+all performance and system functional tests.
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
Code Review / csit.git / blobdiff