When measuring latency, tools such as
mtr are often used. These tools report various metrics, including latency, which is (more often than not) measured in “ms” (milliseconds), along with the Round Trip Time. The RTT is a measure of latency between a client and host, including the time taken for said host to respond.
Round Trip Time can be measured using any of the (nonexhaustive) tools above. We’ll stick to using
ping; an example can be seen when you run
ping test.b-cdn.net -c 4 PING test.b-cdn.net (22.214.171.124): 56 data bytes 64 bytes from 126.96.36.199: icmp_seq=0 ttl=57 time=14.524 ms 64 bytes from 188.8.131.52: icmp_seq=1 ttl=57 time=15.309 ms 64 bytes from 184.108.40.206: icmp_seq=2 ttl=57 time=15.215 ms 64 bytes from 220.127.116.11: icmp_seq=3 ttl=57 time=15.992 ms --- test.b-cdn.net ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 14.524/15.260/15.992/0.520 ms
A quick refresher on how TCP connections work: when a connection is established, a client needs to send a SYNchronize packet, which is succeeded by the intermediate SYN-ACK state and finally, if everything goes well, the client will receive an ACKnowledge response from the host.
Having said that, we’re taking a look at the last line (this can vary with different versions of the
ping binary): the information shown refers to the “round-trip,” or RTT. The time (in milliseconds here) is the total amount of time taken for a “request.” This includes the time taken for SYNchronization, followed by the time for said packet to be sent (in this case, an ICMP echo) and the time taken for a reply to be ACKnowledged and received. When you see suboptimal latency, this can be caused by a variety of issues:
pingrequests (this consequently affects both latency and round trip time)
Round Trip Time (RTT) is an important measure of web performance. For the most part, when measured under “standard” conditions (i.e. uncongested network, acceptable server load), it can provide valuable insight into the performance of existing routes. With deprioritization, ICMP responses can occasionally be lost or be delayed significantly; however, in most cases, routers will either block or accept requests (deprioritization is less popular than outright blocking ICMP requests; they make it more difficult to diagnose issues pertaining to routing and latency).
In essence, RTT is a performance metric returned by
traceroute, and many other latency monitors. It is important to understand this metric as it bundles both the time taken to reach the host (using your ISP's routes) and back (using a host's routes). The routes taken to reach a host and back are not necessarily the same, which is why this metric is so useful for both end-users and network administrators alike.
Latency is a measure of how long something takes to occur from the time it is requested (it is usually measured in 'ms' or milliseconds for Internet traffic).
Ping is a tool used to measure latency, on the 3rd layer, to either a local or remote host.
Traceroute is a network diagnostic tool used for finding the path taken by a network packet to reach a destination IP.
Round Trip Time is a measure of how long a packet takes to reach a host, and back.