Re: Frustrating network latency issue on NetBSD 6.1

[christos%astron.com@localhost (Christos Zoulas)]

In article <20130620091543.GA29154%SDF.ORG@localhost>,
Mayuresh  <mayuresh%acm.org@localhost> wrote:
>On Wed, Jun 19, 2013 at 11:53:42AM -0400, Greg Troxel wrote:
>> Use ping, not ssh, to be able to have a more isolated test case and get
>> quantitative data.  In particular, separate loss from delay; both
>> present as delay over TCP.
>64 bytes from 192.168.169.1: icmp_seq=0 ttl=64 time=6.781 ms
>64 bytes from 192.168.169.1: icmp_seq=1 ttl=64 time=2.283 ms
>64 bytes from 192.168.169.1: icmp_seq=2 ttl=64 time=1.982 ms
>64 bytes from 192.168.169.1: icmp_seq=3 ttl=64 time=4.147 ms
>64 bytes from 192.168.169.1: icmp_seq=4 ttl=64 time=2.320 ms
>64 bytes from 192.168.169.1: icmp_seq=5 ttl=64 time=2.520 ms
>64 bytes from 192.168.169.1: icmp_seq=6 ttl=64 time=1.993 ms
>64 bytes from 192.168.169.1: icmp_seq=8 ttl=64 time=2.595 ms
>64 bytes from 192.168.169.1: icmp_seq=9 ttl=64 time=1.951 ms
>64 bytes from 192.168.169.1: icmp_seq=10 ttl=64 time=2.224 ms
>64 bytes from 192.168.169.1: icmp_seq=14 ttl=64 time=1.960 ms
>64 bytes from 192.168.169.1: icmp_seq=17 ttl=64 time=3.283 ms
>64 bytes from 192.168.169.1: icmp_seq=19 ttl=64 time=1.937 ms
>64 bytes from 192.168.169.1: icmp_seq=22 ttl=64 time=2.325 ms
>64 bytes from 192.168.169.1: icmp_seq=23 ttl=64 time=1.960 ms
>64 bytes from 192.168.169.1: icmp_seq=24 ttl=64 time=1.965 ms
>^C
>----router PING Statistics----
>25 packets transmitted, 16 packets received, 36.0% packet loss
>round-trip min/avg/max/stddev = 1.937/2.639/6.781/1.253 ms
>
>I think 36% is a large number for packet loss?

It is a miracle that you can actually type through it.

christos