Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here are parts of route cache from three different servers that are NOT under high load.

# ip route show cache | grep -B 1 rtt

local from dev lo 
    cache <local>  mtu 16436 rtt 106ms rttvar 155ms cwnd 7 advmss 16396 hoplimit 64
local from dev lo 
    cache <local>  mtu 16436 rtt 145ms rttvar 130ms cwnd 6 advmss 16396 hoplimit 64
local from dev lo 
    cache <local>  mtu 16436 rtt 172ms rttvar 205ms cwnd 5 advmss 16396 hoplimit 64

Why may be rtt so high and so noisy (rttvar is quite high too) ? How can I interpret these values?

share|improve this question
up vote 2 down vote accepted

Values below 200 msec (TCP_RTO_MIN) for the RTT are meaningless. Values below 250 msec for the rttvar are meaningless (because the other side may not have timers that are sufficiently accurate). The RTT/RTTVAR measurements are irrelevant on such fast interfaces.

From include/net/tcp.h:

#define TCP_RTO_MIN     ((unsigned)(HZ/5))

From net/ipv4/tcp_input.c:

     * 1. If rtt variance happened to be less 50msec, it is hallucination.
     *    It cannot be less due to utterly erratic ACK generation made
     *    at least by solaris and freebsd.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.