[ale] Measuering Latency

[jkf at wolfnet.org (Jason Fritcher)]

Christopher Fowler wrote:
> Is there a better way to get these numbers?
>   

Have you looked at mtr for testing latencies? If not, its an awesome 
tool, a combination of traceroute and ping, 
http://www.bitwizard.nl/mtr/. I really like it because just knowing you 
have high latencies is not nearly as useful as knowing what hop is 
causing the problem. In report mode, mtr can generate output similar to 
the following that you could parse and look for abnormally high 
latencies. These reports also make good clue sticks to use on support 
critters. :)

$ mtr -r -c 10 www.google.com
HOST: comstar                     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. 169.254.1.1                   0.0%    10    0.2   0.2   0.2   0.4   0.1
  2. 72.9.242.1                    0.0%    10    0.6   1.2   0.3   2.2   0.5
  3. L3-ATL-1.gnax.net             0.0%    10    1.8   1.5   0.8   2.8   0.7
  4. atl-core-a-gi3-6.gnax.net     0.0%    10    1.4   1.7   1.1   2.5   0.5
  5. 209.51.130.209                0.0%    10    1.5   1.6   0.7   3.5   0.8
  6. aix.pr1.atl.google.com        0.0%    10    1.8   6.0   1.2  43.2  13.1
  7. 72.14.236.12                  0.0%    10    1.8   1.6   0.9   2.4   0.5
  8. 72.14.238.137                 0.0%    10   15.0  17.6  14.7  39.0   7.5
  9. 64.233.175.111                0.0%    10   15.4  15.5  14.6  17.5   0.8
 10. 72.14.232.25                  0.0%    10   17.9  17.8  17.1  18.4   0.5
 11. yo-in-f99.google.com          0.0%    10   14.8  15.3  14.5  17.2   0.8

-- 
 Jason K. Fritcher
  jkf at wolfnet.org