Latte – for accurate network latency testing of the protocols used by most applications SockPerf (for Linux) and Latte (for Windows) produce the most relevant results
Allow Latte through the Windows firewall
C:\>netsh advfirewall firewall add rule program=C:\PC_TOOLS\LattePortable\latte.exe name=“latte“ protocol=any dir=in action=allow enable=yes profile=ANY
Run latency tests
On the receiver start latte.exe (run it from the CMD window not from PowerShell)
latte -a <Receiver IP address>:<port> -i <iterations>
Around 65000 iterations is long enough to return representative results
Any available port number is fine.
If the VM has an IP address of 10.0.0.4 the command would look like this
C:\>PC_TOOLS\LattePortable\latte.exe -a 192.168.27.105:5005 -i 65100
On the sender start latte.exe (run it from the CMD window not from PowerShell)
latte -c -a <Receiver IP address>:<port> -i <iterations>
The resulting command is the same as on the receiver except with the addition of -c to indicate that this is the client or sender
C:\>PC_TOOLS\LattePortable\latte.exe -c -a 192.168.127.105:5005 -i 65100
Note that both commands include the same IP@ the address of the receiver
I ran the test fives times and the lowest latency score I received with my default setup was a latency of 89 usec (microseconds) – that’s 89 millionths of a second