X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=blobdiff_plain;f=test_spec%2Fvswitchperf_ltd.md;h=6f02a6eb41c361986e546fc2183a1d2aa8ce3c0c;hb=cb5400b079ec8aacfd6dac73cbf59b74bbcb4e1e;hp=dc823538632514ed08dd76eb0cb3f98518d2d0b8;hpb=d9c1a522d6a77eb4a61b674e65065b32c3d09b5b;p=vswitchperf.git diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index dc823538..6f02a6eb 100755 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -306,6 +306,40 @@ The following represents possible deployments which can help to determine the pe +-----------------------------------------------------------------------------------------------------------+__| + - HOST 1(Physical port â virtual switch â VNF â virtual switch â Physical port) â HOST 2(Physical port â virtual switch â VNF â virtual switch â Physical port) + +
+
+ +--------------------------------------------+ +------------------------------------------+
+ | +---------------------------------+ | | +--------------------------------+ |
+ | | Application | | | | Application | |
+ | +----------------------------+----+ | | +-------------------------+------+ |
+ | ^ | | | ^ | |
+ | | v | | | v |
+ | +-------+----------+ +------------------+ | | +---------+--------+ +----------------+ |
+ | | Logical port 0 | | Logical port 1 | | | | Logical port 0 | |Logical port 1 | |
+ +-+------------------+--+------------------+-+ +-+------------------+--+------+---------+-+
+ ^ | ^ |
+ | | | |
+ | v | v
+ +-+-------+----------+--+------------------+-+ +-+---------+--------+--+----------------+-+
+ | | Logical port 0 | | Logical port 1 | | | | Logical port 0 | | Logical port 1 | |
+ | +------------------+ +----------+-------+ | | +------------------+ +------+---------+ |
+ | ^ | | | ^ | |
+ | | | | | | | |
+ | | vswitch v | | | vswitch v |
+ | +--------+---------+ +------------------+ | | +---------+--------+ +----------------+ |
+ | | phy port | | phy port | | | | phy port | | phy port | |
+ +-+--------+---------+--+----------+-------+-+ +-+---------+--------+--+------+---------+-+
+ ^ +---------------------------------------+ |
+ | v
+ +----------+----------------------------------------------------------------------------------+-----------+
+ | |
+ | traffic generator |
+ | |
+ +---------------------------------------------------------------------------------------------------------+
+
+
**Note:** For tests where the traffic generator and/or measurement receiver are implemented on VM and connected to the virtual switch through vNIC, the issues of shared resources and interactions between the measurement devices and the device under test must be considered.
####General Methodology:
@@ -574,7 +608,7 @@ The starting point for defining the suite of tests for benchmarking the performa
- Hardware details including:
- Platform details.
- Processor details.
- - Memory information (type and size).
+ - Memory information (see below)
- Number of enabled cores.
- Number of cores used for the test.
- Number of physical NICs, as well as their details (manufacturer, versions, type and the PCI slot they are plugged into).
@@ -597,6 +631,18 @@ The starting point for defining the suite of tests for benchmarking the performa
- Number vNIC interrupt configuration.
- Thread affinitization for the applications (including the vSwitch itself) on the host.
- Details of Resource isolation, such as CPUs designated for Host/Kernel (isolcpu) and CPUs designated for specific processes (taskset).
+ - Memory Details
+ - Total memory
+ - Type of memory
+ - Used memory
+ - Active memory
+ - Inactive memory
+ - Free memory
+ - Buffer memory
+ - Swap cache
+ - Total swap
+ - Used swap
+ - Free swap
- Test duration.
- Number of flows.
- Traffic Information:
@@ -915,7 +961,7 @@ The starting point for defining the suite of tests for benchmarking the performa
**Description**:
- This test measures the DUT's Max Forwarding Rate when the Offered Load is varied between the throughput and the Maximum Offered Load for fixed length frames at a fixed time interval. The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams). The throughput is the maximum offered load with 0% frame loss (measured by the prerequisite test), and the Maximum Offered Load (as defined by [RFC2885]) is _"the highest number of frames per second that an external source can transmit to a DUT/SUT for forwarding to a specified output interface or interfaces"_.
+ This test measures the DUT's Max Forwarding Rate when the Offered Load is varied between the throughput and the Maximum Offered Load for fixed length frames at a fixed time interval. The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams). The throughput is the maximum offered load with 0% frame loss (measured by the prerequisite test), and the Maximum Offered Load (as defined by [RFC2285]) is _"the highest number of frames per second that an external source can transmit to a DUT/SUT for forwarding to a specified output interface or interfaces"_.
Traffic should be sent to the DUT at a particular rate (TX rate) starting with TX rate equal to the throughput rate. The rate of successfully received frames at the destination counted (in FPS). If the RX rate is equal to the TX rate, the TX rate should be increased by a fixed step size and the RX rate measured again until the Max Forwarding Rate is found.
@@ -1057,15 +1103,53 @@ The starting point for defining the suite of tests for benchmarking the performa
The aim of this test is to determine the maximum forwarding rate of the DUT when forwarding broadcast traffic. For each frame previously defined under [Default Test Parameters](#DefaultParams), the traffic should be set up as broadcast traffic. The traffic throughput of the DUT should be measured.
+ The test should be conducted with at least 4 physical ports on the DUT. The number of ports used MUST be recorded.
+
+ As broadcast involves forwarding a single incoming packet to several destinations, the latency of a single packet is defined as the average of the latencies for each of the broadcast destinations.
+
+ The incoming packet is transmitted on each of the other physical ports, it is not transmitted on the port on which it was received. The test MAY be conducted using different broadcasting ports to uncover any performance differences.
+
**Expected Result**:
- **Metrics collected**
+ **Metrics collected**:
The following are the metrics collected for this test:
- The forwarding rate of the DUT when forwarding broadcast traffic.
+ - The minimum, average & maximum packets latencies observed.
+
+ **Deployment scenario**:
+
+ - Physical â virtual switch 3x physical.