EasyManua.ls Logo

Albedo xGenius - Page 203

Albedo xGenius
322 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Automatic Performance Tests
191
RTT test Menu that provides access to a panel with the baseline RTT
test results if this test has been configured to run. This panel
contains Status information (Idle, In progress, Done, Error),
the Baseline RTT result and the Window size derived from
the expected IR settings and the baseline RTT. This window
size will be used to set a series of suboptimal test cases for
the window sweep test and it will also be used to run the
throughput test and compute the efficiency and latency
results. The minimum allowed window size is 16 KB and
starting from this, it can take only values that are multiples of
8 KB. If the BDP does not match with any of the allowed val-
ues then the window size is rounded to the closer upper
allowed value.
If you are running a bidirectional test, the RTT results panel
will display information about each individual transmission
directions.
Window sweep test This is a menu that provides access to the window sweep
results when this test has been configured to run. The win-
dow sweep result displays status information (Idle, In pro-
gress, Done, Error) and the results organized in a table
where each row represents the results for one specific trans-
mission window. The results the test provides for each row
are:
Window size: Window size used to generate TCP traffic in
the current test iteration. It is always a fraction of the win-
dow size computed in the RTT test with the constrains of
being at least 16 KB and being a multiple of 8 KB.
Connections: Number of concurrent TCP connections
occurring in the current test iteration. It is always one for
the current RFC 6349 implementation.
Theoretical throughput: It is the throughput computed for
the given window. It takes into account the potential
throughput degradation derived from an incorrect window
setting and the payload to frame length ratio for the TCP
protocol and the configured MTU value.
Throughput: Measured TCP throughput for the given win-
dow. All Ethernet, IPv4 and TCP overhead is not taken into
account for the throughput calculation. The measured
throughput is always smaller or equal to the theoretical
value.
Table 7.12: RFC 6349 Results
Setting Description

Table of Contents