Measuring Latency

When mtping receives a response, it displays the time between when the request was sent and when that response was received.  It also includes a count of how many times the request was repeated.  For example:

host-16: mtping dataexpedition.com ACT_IDSTR dataexpedition.com (70.164.67.132:8080) Response 0 of 208 bytes after 0 repeats in 151ms (Version 2/0): servedat - 1.15.0 July 2013 - DEI, DOC-1.15.0 MTP-osx-3.15.11 811 00000001: ExpeDat-1.15A Data Expedition Inc., DataExpedition.com Server Statistics (11400): Name: servedat Version: 1.15.0 Platform: osx Clock: Fri Aug 2 15:52:23 2013 Clock Skew: 0 seconds Delimiter: / Load: Current: 0, MaxConfig: 2, MaxStart: 2, TotalStart: 205 Capacity: 10 Up Time: 1.28 weeks Config Time: 4.12 days Idle Time: 44.4 minutes Errors: Errors 0, Failures: 0, Warnings: 0, Denials: 1

The above output indicates a latency of 151 milliseconds.

To continuously monitor latency, use the "-c" option to specify multiple requests:

host-17: mtping -c 3 DataExpedition.com:8080 ACT_PING dataexpedition.com (70.164.67.132:8080) 0 bytes from 70.164.67.132: count=0 repeats=0 time=60 ms 0 bytes from 70.164.67.132: count=1 repeats=0 time=17 ms 0 bytes from 70.164.67.132: count=2 repeats=0 time=15 ms 0 bytes from 70.164.67.132: count=3 repeats=0 time=17 ms --- dataexpedition.com mtping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 15/27.250/60 ms

Latency versus Round Trip Time

The latency measured by mtping may be significantly higher than the network round-trip-time due to the following factors:

For a more accurate assessment of latency, continuously monitor over a significant period of time.