| Field |
Description |
Values |
Default |
| Improve Time To Test |
| Skip to next load when iteration fails |
Available when Trial Duration is set to Time.
Select to abort an iteration and start the next iteration when any of the criteria fail.
- The frame loss percentage exceeds the value set in Acceptable frame loss.
- The latency exceeds the value set in Max latency.
This option monitors the Dropped Frame Count to detect frame loss. If the first frame is dropped, loss is not detected due to the lack of a starting frame sequence number. In this case, the iteration is not skipped and there is no improvement in test time.
| Note: By default the RFC 2544 Throughput test uses the Inter-arrival Time results mode. When this option is selected, it uses the Latency-Jitter results mode if the card supports it. Otherwise, it uses the Basic results mode. |
|
N/A |
Cleared |
| Enable Turbo Iteration |
Available when
- Trial Duration is set to Time
- RFC 5180 is disabled
- Enable Traffic Group Options is cleared
Select to add a turbo sequence to the test sequence, which includes the Turbo Loop and Iterate Turbo Throughput commands. During a turbo iteration, the traffic load is set dynamically and results gathering is disabled. When the maximum throughput is detected in the Turbo Loop, an iteration is performed using the time set in Trial Duration with the maximum successful load and results are collected.
If an iteration fails, the turbo sequence is run again in RETEST mode. In this mode, the turbo load search algorithm is repeated between the initial rate and the last passed load. This sequence is repeated until a passed throughput is found or the minimum failed load is reached.
If there is no previously passed load, then Turbo Iteration is disabled and the load loop is run as a normal test and uses the Back-off specified by load search algorithm.
| NOTE: By default the RFC 2544 Throughput test uses the Inter-arrival Time results mode. When this option is selected, it uses the Latency-Jitter results mode if the card supports it. Otherwise, it uses the Basic results mode. |
|
CAUTION: Turbo Iteration uses the Interesting Streams feature, with the following limitations.
Dropped frames are not counted until at least one frame is received. Any frames that are dropped before a frame arrives are not counted.
Setting the Interesting Stream filter to RxFrameCount =0 will not identify streams with 100% frame loss.
For a failure threshold to be recognized, the condition must be met by an individual stream. For example, if the threshold for dropped frames is set to 100, the threshold will be crossed when any individual stream counts 100 dropped frames. If two streams lose 60 frames each, the threshold is not crossed.
|
|
N/A |
Cleared |
| Turbo Duration |
Duration of a turbo iteration. Must be less than Trial Duration. |
1-30 |
5 |
| Traffic Load for Throughput Search |
| Mode |
Select one of the following throughput options:
- Step: Increases the test load with each iteration by the percentage
specified by Step rate
- Binary: Searches for the throughput value using a binary search
algorithm
- Combine: Begins in Step mode, then switches to Binary mode
when an iteration fails
|
Step, Binary, Combo |
Binary |
| Rate lower limit |
Enter the minimum load for the test, as a percentage of the wire rate.
This field is enabled only if Mode is set to Binary. |
0.001% ~ 100% |
1% |
| Rate upper limit |
Enter the maximum load for the test, as a percentage of the wire rate |
0.001% ~ 100% |
100% |
|
Initial rate
|
Enter the initial load in the first iteration, as a percentage of the
wire rate |
0.001% ~ 100% |
10% |
| Step rate |
Enter the rate increment for each successive iteration. This field is
enabled only if Mode is set to Step or Combine. |
0.001% ~ 100% |
10% |
| Resolution |
Enter the finest adjustment possible in load from one iteration to the
next. If the required adjustment for the next iteration is less than this
value, the test stops. This field is enabled only if Mode is set
to Binary or Combine. |
0.001% ~ 100% |
1% |
| Back-off |
Enter the rate the load decreases after the DUT/SUT fails at the current
load. This value may be an integer or decimal. This field is enabled only
if Mode is set to Binary or Combine. |
0.001% ~ 99.999% |
50% |
| Acceptable frame loss |
Enter the number of frames that can be lost without frame loss being
declared (the iteration fails).
|
NOTE: The RFC does not define acceptable frame loss.
It requires zero frame loss.
|
|
0%-100% |
0% |
| Ignore lower/upper limits |
Select the checkbox to eliminate guesswork in attempting to define
the range that yields the true throughput result. The Rate lower
limit and Rate upper limit values focus testing
on a specified range. If throughput is not found within this range, the
range expands either to 100% (upward adjustment) or 0% (downward adjustment).
The test continues until the throughput rate is found or the load reaches
either 0% or 100%.
|
N/A |
Cleared |
| Throughput Threshold |
| Max latency |
Select the checkbox to enable the maximum latency threshold test.
In the text box, enter the maximum (in microseconds) of all the average
latencies determined on each receive port in the test. If the threshold
is reached, then the test iteration fails.
|
0.01-4294967295 |
Cleared
30
|
| Out of sequence |
Select the checkbox to enable the out-of-sequence test. In the text
box, enter the number of out-of-order frames on each receive port that,
if exceeded, causes the test iteration to fail.
Not available when Skip to next load when iteration fails or Enable Turbo Iteration is enabled.
|
0-2147483647 |
Cleared
0
|