Connection Analysis
|
MSTR02: The trip time for this connection is too erratic.
Trip times are a crucial measure to the performance of a connection because the trip time dictates the maximum achievable throughput speed between the server and the client. If the trip times are erratic it is a sure sign of problems on the route. As an example imagine driving from home to your local airport, it is most probably a journey that you have done several times. If there are no hold ups on the road your time to the airport should be the result of the road speed limit divided by the distance. For example if the distance was 30 miles and the road speed limit was 60 miles per hour then the trip time to the airport and back should be about 1 hour. In an ideal world if the road is not congested then you would expect to take about an hour each time you drive to the airport and back. That said, if the road to the airport is busy with lots of traffic and you hit a few red lights your trip time will be extended by varying amounts depending of the extent of the congestion/regulation. During the connection test several trip time measures are taken and are reported to provide a baseline for understanding the overall condition of the route between server and client. It is important to note that if the client's connection speed is high then the impact of an erratic trip delay will be more extreme. Consider a normal trip latency of 25ms which will support a TCP maximum speed using a single window of about 20Mbps. If the trip latency varies by only 5ms to 30ms then the speed will drop to just 17Mbps. Obviously the higher the connection capacity speed the bigger the impact. To learn more trip latency click here. Need more help or have questions, please contact us. |