As you will see in this example the forced idle for the connection is quite high (32%). Read the section below to learn more about what this measure shows and how it is calculated.
This measure identifies inherent TCP idle time invoked because the end-to-end latency for the connection exceeds the TCP transmit time for the window size being used. The TCP stack is forced to idle for the length of this delay. The percentage of the route latency time that is forced TCP idle time allows users to assess the capacity for a connection to sustain more than one TCP session with little or no degradation to other TCP sessions.
For example, if a connection shows 50 percent forced idle another FTP download session could be run on the same route with little to no impact to the first download session. In this case, if a download service supports multiple connections the throughput could be doubled by allowing the transfer to use more than one connection. Forced idle time is also a benefit to HTTP as HTTP will operate more than one concurrent transfer simultaneously. |
