Tahhan, et al. Expires September 22, 2016 [Page 1]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 2]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 3]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 4]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 5]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 6]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 7]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 8]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 9]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 10]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 11]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 12]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 13]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 14]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 15]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 16]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 17]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 18]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 19]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 20]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
Tahhan, et al. Expires September 22, 2016 [Page 21]
-\f
+
Internet-Draft Benchmarking vSwitches March 2016
`RFC2544 <https://www.rfc-editor.org/rfc/rfc2544.txt>`__).
- Following may also be collected as part of this test, to determine
the vSwitch's performance footprint on the system:
+
- CPU core utilization.
- CPU cache utilization.
- Memory footprint.
This test evaluates standard switch performance benchmarks for the scenario where an
Overlay Network is deployed for all paths through the vSwitch. Overlay Technologies covered
(replacing <tech> in the test name) include:
+
- VXLAN
- GRE
- NVGRE
- GENEVE
Performance will be assessed for each of the following overlay network functions:
+
- Encapsulation only
- De-encapsulation only
- Both Encapsulation and De-encapsulation
For each native packet, the DUT must perform the following operations:
+
- Examine the packet and classify its correct overlay net (tunnel) assignment
- Encapsulate the packet
- Switch the packet to the correct port
- For each encapsulated packet, the DUT must perform the following operations:
+ For each encapsulated packet, the DUT must perform the following operations:
+
- Examine the packet and classify its correct native network assignment
- De-encapsulate the packet, if required
- Switch the packet to the correct port
The following are the metrics collected for this test:
- The forwarding rate in Frames Per Second (FPS) and Mbps of the DUT
- for each delta to the maximum forwarding rate and for each frame
- size.
+ for each delta to the maximum forwarding rate and for each frame
+ size.
- The average latency for each delta to the maximum forwarding rate and
- for each frame size.
+ for each frame size.
- CPU and memory utilization may also be collected as part of this
- test, to determine the vSwitch's performance footprint on the system.
+ test, to determine the vSwitch's performance footprint on the system.
- Any failures experienced (for example if the vSwitch crashes, stops
processing packets, restarts or becomes unresponsive to commands)
- when the offered load is above Maximum Throughput MUST be recorded
- and reported with the results.
+ when the offered load is above Maximum Throughput MUST be recorded
+ and reported with the results.
.. 3.2.3.4
.. 3.2.3.6.1
Test ID: LTD.Stress.RFC2544.0PacketLoss
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**Title**: RFC 2544 0% Loss CPU OR Memory Stress Test
**Prerequisite Test**:
**Note:** Stress in the test ID can be replaced with the name of the
component being stressed, when reporting the results:
LTD.CPU.RFC2544.0PacketLoss or LTD.Memory.RFC2544.0PacketLoss
+
.. 3.2.3.7
Summary List of Tests
Code Review / vswitchperf.git / commitdiff