For ages now I've been putting big ping times down to a bad connection, but it obviously isn't the case. While my client was frozen solid reporting huge 8 second ping times, a parallel "ping" on the same machine reports this ...
PING sim696.agni.lindenlab.com (69.25.105.12

: 56 data bytes
64 bytes from 69.25.105.128: icmp_seq=0 ttl=45 time=167.957 ms
64 bytes from 69.25.105.128: icmp_seq=1 ttl=45 time=166.207 ms
64 bytes from 69.25.105.128: icmp_seq=2 ttl=45 time=168.532 ms
64 bytes from 69.25.105.128: icmp_seq=3 ttl=45 time=168.840 ms
64 bytes from 69.25.105.128: icmp_seq=4 ttl=45 time=167.180 ms
64 bytes from 69.25.105.128: icmp_seq=5 ttl=45 time=169.522 ms
64 bytes from 69.25.105.128: icmp_seq=6 ttl=45 time=169.061 ms
64 bytes from 69.25.105.128: icmp_seq=7 ttl=45 time=168.197 ms
64 bytes from 69.25.105.128: icmp_seq=8 ttl=45 time=166.257 ms
64 bytes from 69.25.105.128: icmp_seq=9 ttl=45 time=168.545 ms
--- sim696.agni.lindenlab.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 166.207/168.030/169.522/1.081 ms
so "ping sim" is the amount of time it takes a sim to reply to the client and is not a simple ping at all ?
The same sim had just 3 AVs, a high FPS of over 700, and the highest peak I saw on the stats was 3ms for "run tasks".
Something must be amiss somewhere surely ?