diff options
Diffstat (limited to 'test_spec/vswitchperf_ltd.md')
| -rw-r--r-- | test_spec/vswitchperf_ltd.md | 78 |
1 files changed, 41 insertions, 37 deletions
diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 98b82d90..7fbd2cc2 100644 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -166,38 +166,40 @@ The following represents possible deployments which can help to determine the pe - Physical port → virtual switch → VNF → virtual switch → VNF → virtual switch → physical port. <pre><code> - __ - +---------------------------------------------------+ +---------------------------------------------------+ | - | Guest 1 | | Guest 2 | | - | +-------------------------------------------+ | | +-------------------------------------------+ | | - | | Application | | | | Application | | | - | +-------------------------------------------+ | | +-------------------------------------------+ | | - | ^ : | | ^ : | | - | | | | | | | | | Guest - | : v | | : v | | - | +---------------+ +---------------+ | | +---------------+ +---------------+ | | - | | logical port 0| | logical port 1| | | | logical port 0| | logical port 1| | | - +---+---------------+-----------+---------------+---+ +---+---------------+-----------+---------------+---+__| - ^ : ^ : - | | | | - : v : v __ - +---+---------------+----------+---------------+------------+---------------+-----------+---------------+---+ | - | | port 0 | | port 1 | | port 2 | | port 3 | | | - | +---------------+ +---------------+ +---------------+ +---------------+ | | - | ^ : ^ : | | - | | | | | | | Host - | : +--------------------+ v | | - | +--------------+ +--------------+ | | - | | phy port | vswitch | phy port | | | - +---+--------------+--------------------------------------------------------------------+--------------+----+__| - ^ : - | | - : v - +-----------------------------------------------------------------------------------------------------------+ - | | - | traffic generator | - | | - +-----------------------------------------------------------------------------------------------------------+ + + __ + +----------------------+ +----------------------+ | + | Guest 1 | | Guest 2 | | + | +---------------+ | | +---------------+ | | + | | Application | | | | Application | | | + | +---------------+ | | +---------------+ | | + | ^ | | | ^ | | | + | | v | | | v | | Guests + | +---------------+ | | +---------------+ | | + | | logical ports | | | | logical ports | | | + | | 0 1 | | | | 0 1 | | | + +---+---------------+--+ +---+---------------+--+__| + ^ : ^ : + | | | | + : v : v _ + +---+---------------+---------+---------------+--+ | + | | 0 1 | | 3 4 | | | + | | logical ports | | logical ports | | | + | +---------------+ +---------------+ | | + | ^ | ^ | | | Host + | | L-----------------+ v | | + | +--------------+ +--------------+ | | + | | phy ports | vSwitch | phy ports | | | + +---+--------------+----------+--------------+---+_| + ^ : ^ : + | | | | + : v : v + +--------------------------------------------------+ + | | + | traffic generator | + | | + +--------------------------------------------------+ + </code></pre> - Physical port → virtual switch → VNF. @@ -565,17 +567,17 @@ The following represents possible deployments which can help to determine the pe - #####Test ID: LTD.Throughput.RFC2544.SystemRecoveryTime **Title**: RFC 2544 System Recovery Time Test - **Prerequisite Test**: N\A + **Prerequisite Test** LTD.Throughput.RFC2544.PacketLossRatio **Priority**: **Description**: - The aim of this test is to determine the length of time it takes the DUT to recover from an overload condition for a constant load (fixed length frames at a fixed interval time). The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams), traffic should be sent to the DUT under normal conditions. During the duration of the test and while the traffic flows are passing though the DUT, at least one situation leading to an overload condition for the DUT should occur. The time from the start of the overload condition to when the DUT returns to normal operations should be measured to determine recovery time. Prior to overloading the DUT, one should record the average latency for 100 packets forwarded through the DUT. + The aim of this test is to determine the length of time it takes the DUT to recover from an overload condition for a constant load (fixed length frames at a fixed interval time). The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams), traffic should be sent to the DUT under normal conditions. During the duration of the test and while the traffic flows are passing though the DUT, at least one situation leading to an overload condition for the DUT should occur. The time from the end of the overload condition to when the DUT returns to normal operations should be measured to determine recovery time. Prior to overloading the DUT, one should record the average latency for 10,000 packets forwarded through the DUT. - The suggested overload condition would be to transmit traffic at a very high frame rate to the DUT, for at least 60 seconds, then reduce the frame rate to the DUT by half; A number of time-stamps should be recorded: - - Record the time-stamp at which the frame rate was halved and record a second time-stamp at the time of the last frame lost. The recovery time is the difference between the two timestamps. - - Record the average Latency for 100 frames after the last frame loss and continue to record average latency measurements for every 100 frames, when latency returns to pre-overload levels record the time-stamp. + The overload condition SHOULD be to transmit traffic at a very high frame rate to the DUT (150% of the maximum 0% packet loss rate as determined by LTD.Throughput.RFC2544.PacketLossRatio or line-rate whichever is lower), for at least 60 seconds, then reduce the frame rate to 75% of the maximum 0% packet loss rate. A number of time-stamps should be recorded: + - Record the time-stamp at which the frame rate was reduced and record a second time-stamp at the time of the last frame lost. The recovery time is the difference between the two timestamps. + - Record the average latency for 10,000 frames after the last frame loss and continue to record average latency measurements for every 10,000 frames, when latency returns to within 10% of pre-overload levels record the time-stamp. **Expected Result**: @@ -643,6 +645,7 @@ The following represents possible deployments which can help to determine the pe - Any outliers in the Throughput stability. - Any unexpected variation in Throughput stability. - CPU and memory utilization may also be collected as part of this test, to determine the vSwitch's performance footprint on the system. + - The [RFC5481] PDV form of delay variation on the traffic flow, using the 99th percentile. <br/> @@ -684,6 +687,7 @@ The following represents possible deployments which can help to determine the pe - Any outliers in the Throughput stability. - Any unexpected variation in Throughput stability. - CPU and memory utilization may also be collected as part of this test, to determine the vSwitch's performance footprint on the system. + - The [RFC5481] PDV form of delay variation on the traffic flow, using the 99th percentile. <br/> |