[ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Uwe Klein uwe at klein-habertwedt.de
Sun Mar 18 09:39:11 UTC 2012

David J Taylor wrote:
> "John Hasler" <jhasler at newsguy.com> wrote in message 
> news:87sjh7mlqs.fsf at thumper.dhh.gt.org...
>> David J Taylor writes:
>>> But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s up.  I
>>> have been promised an upload speed increase about 18 months ago to 2
>>> Mb/s up, which is more sensible...
>> Such a very high cable download speed is a peak burst speeds on a shared
>> medium.  Your sustained performance is not likely to be more than a
>> fraction of it.
> Speed tests from a number of sites show 30 Mb/s, and that's over several 
> seconds.  I downloaded the Windows-8 64-bit ISO recently, and the 
> 3,583,707,136 bytes took 48 minutes, 24 seconds, which I make about 7.4 
> Mb/s, and the 32-bit ISO was 2,711,396,352 bytes in 27 minutes, so about 
> 13.4 Mb/s.  That was without any download accelerator (no multiple 
> connections).

Sustained transfer speeds are a moot point.

You want to know about chanel delays.
   In absolute, asymmetricness and variation terms.

Regular DSL here has quite large and spread line delays
though speed is much higher delay is similar or slightly larger than
forex ISDN.
PING ( 56(84) bytes of data. ( my first pingable outside node )
64 bytes from icmp_seq=1 ttl=254 time=48.3 ms
64 bytes from icmp_seq=2 ttl=254 time=34.3 ms
64 bytes from icmp_seq=3 ttl=254 time=77.4 ms
64 bytes from icmp_seq=4 ttl=254 time=70.8 ms
64 bytes from icmp_seq=5 ttl=254 time=108 ms
64 bytes from icmp_seq=6 ttl=254 time=89.0 ms
64 bytes from icmp_seq=7 ttl=254 time=109 ms
64 bytes from icmp_seq=8 ttl=254 time=64.1 ms
64 bytes from icmp_seq=9 ttl=254 time=76.1 ms
64 bytes from icmp_seq=10 ttl=254 time=145 ms
64 bytes from icmp_seq=11 ttl=254 time=199 ms
64 bytes from icmp_seq=12 ttl=254 time=104 ms
64 bytes from icmp_seq=13 ttl=254 time=247 ms
64 bytes from icmp_seq=14 ttl=254 time=104 ms


More information about the questions mailing list