Ping Timeout

When MultiPing sends out a packet, it waits a certain amount of time for a response.  The longer it waits, the more resources it needs to use (to keep sockets open), but the more likely that it will get a response.  9999 is a pretty high number – very few packets take longer than this to return.  Some people use 1500 here.

Time interval between hop traces 

MultiPing sends out packets without waiting for other packets to return.  This doesn't mean, however, that it sends out all packets at once (you don’t want to do this, or it might overwhelm your bandwidth).  This is in ms (or 1/1000s of a second).

Packet Size 

The Packet Size can make a considerable difference in latency performance.  Normally, you want to use a relatively small number here.  The default is 56 bytes, but in some cases you might need to lower this. Large packets should be used with great care.  A 1500 byte packet means MultiPing may be sending out 30-50 K per second worth of data, which can cause its own problems (and makes measuring latency more challenging).

Maximum samples held in memory.

Long-term monitoring sessions might start to fill up memory, making things run slower.  If you want to purge off old samples when memory starts to get full, set this.  This defaults to 200000, which will take (very) roughly a megabyte of memory per target.