diff options
| -rw-r--r-- | test_spec/vswitchperf_ltd.md | 22 |
1 files changed, 14 insertions, 8 deletions
diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 66f19740..0b2d308a 100644 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -629,7 +629,7 @@ The following represents possible deployments which can help to determine the pe **Description**: - The aim of this test is to understand the Throughput stability over an extended test duration in order to uncover any outliers. To allow for an extended test duration, the test should ideally run for 24 hours or, if this is not possible, for at least 6 hour. For this test, each frame size must be sent at the highest Throughput with X% packet loss, as determined in the prerequisite test. The default loss percentages to be tested are: + The aim of this test is to understand the Throughput stability over an extended test duration in order to uncover any outliers. To allow for an extended test duration, the test should ideally run for 24 hours or, if this is not possible, for at least 6 hours. For this test, each frame size must be sent at the highest Throughput with X% packet loss, as determined in the prerequisite test. The default loss percentages to be tested are: - X = 0% - X = 10^-7% @@ -642,8 +642,7 @@ The following represents possible deployments which can help to determine the pe The following are the metrics collected for this test: - Throughput stability of the DUT. - - Any outliers in the Throughput stability. - - Any unexpected variation in Throughput stability. + - This means reporting the number of packets lost per time interval and reporting any time intervals with packet loss. An interval of 60s is suggested. - 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. @@ -700,7 +699,13 @@ The following represents possible deployments which can help to determine the pe **Description**: - The aim of this test is to determine the length of time it takes the DUT to recover from a reset. For each frame size 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 through the DUT, the DUT should be reset and the Reset time measured. The Reset time is the total time that a device is determined to be out of operation and includes the time to perform the reset and the time to recover from it (cf. [RFC6201]) + The aim of this test is to determine the length of time it takes the DUT to recover from a reset. + + Two reset methods are defined - planned and unplanned. A planned reset requires stopping and restarting the virtual switch by the usual 'graceful' method defined by it's documentation. An unplanned reset requires simulating a fatal internal fault in the virtual switch - for example by using kill -SIGKILL on a Linux environment. + + Both reset methods SHOULD be exercised. + + For each frame size 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 through the DUT, the DUT should be reset and the Reset time measured. The Reset time is the total time that a device is determined to be out of operation and includes the time to perform the reset and the time to recover from it (cf. [RFC6201]). [RFC6201] defines two methods to measure the Reset time: - Frame-Loss Method: which requires the monitoring of the number of lost frames and calculates the Reset time based on the number of frames lost and the offered rate according to the following formula: @@ -725,13 +730,14 @@ The following represents possible deployments which can help to determine the pe **Metrics collected** The following are the metrics collected for this test: - - Average Reset Time. + - Average Reset Time over the number of trials performed. Results of this test should include the following information: + - The reset method used. - Throughput in Fps and Mbps. - - Average Frame Loss. - - Average Reset Time in milliseconds. - - Number of trials. + - Average Frame Loss over the number of trials performed. + - Average Reset Time in milliseconds over the number of trials performed. + - Number of trials performed. - Protocol: IPv4, IPv6, MPLS, etc. - Frame Size in Octets - Port Media: Ethernet, Gigabit Ethernet (GbE), etc. |