Prev: Extended deadline (15 July 2010): CACS Singapore [EI Compendex,ISTP,IEEE Xplore]
Next: ARP cache size increase: how to find if this is necessary?
From: Marc Haber on 31 May 2010 09:21
Günther Schwarz <strap(a)gmx.de> wrote:
>Marc Haber wrote:
>> Günther Schwarz <strap(a)gmx.de> wrote:
>>>Today it works better with 100-300 kb/s for a ssh copy from a reliable
>>>host with good bandwith. Results for a ping:
>>>
>>>$ ping www.heise.de
>>>PING www.heise.de (193.99.144.85) 56(84) bytes of data. 64 bytes from
>>>www.heise.de (193.99.144.85): icmp_seq=1 ttl=245 time=447 ms 64 bytes
>>>from www.heise.de (193.99.144.85): icmp_seq=2 ttl=245 time=383 ms 64
>>>bytes from www.heise.de (193.99.144.85): icmp_seq=3 ttl=245 time=400 ms
>>>^C64 bytes from www.heise.de (193.99.144.85): icmp_seq=4 ttl=245
>>>time=395 ms
>>
>> That's a typical EDGE latency. HSDPA should be in the 100 ms range.
>
>Performance is indeed comparable to another SIM-card on a location where
>no UMTS is available. So is Samsung to blame for the invention of
>cheating electronics? ;-)

Probably. Can you try with a different device, probably borrowed from
a friend?

Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
From: Rick Jones on 1 Jun 2010 14:48
> >$ ping www.heise.de
> >PING www.heise.de (193.99.144.85) 56(84) bytes of data.
> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=1 ttl=245 time=447 ms
> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=2 ttl=245 time=383 ms
> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=3 ttl=245 time=400 ms
> >^C64 bytes from www.heise.de (193.99.144.85): icmp_seq=4 ttl=245 time=395
> >ms

> That's a typical EDGE latency. HSDPA should be in the 100 ms range.

Wow - that is also getting close to the round-trip latency one would
see using a GEO satellite both ways - O(500ms).

rick jones
--
It is not a question of half full or empty - the glass has a leak.
The real question is "Can it be patched?"
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
From: Marc Haber on 5 Jun 2010 11:32
Rick Jones <rick.jones2(a)hp.com> wrote:
>> >$ ping www.heise.de
>> >PING www.heise.de (193.99.144.85) 56(84) bytes of data.
>> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=1 ttl=245 time=447 ms
>> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=2 ttl=245 time=383 ms
>> >64 bytes from www.heise.de (193.99.144.85): icmp_seq=3 ttl=245 time=400 ms
>> >^C64 bytes from www.heise.de (193.99.144.85): icmp_seq=4 ttl=245 time=395
>> >ms
>
>> That's a typical EDGE latency. HSDPA should be in the 100 ms range.
>
>Wow - that is also getting close to the round-trip latency one would
>see using a GEO satellite both ways - O(500ms).

Plain GPRS has 700-800 ms which easily exceeds the full second if the
line is actually in use.

Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
First  |  Prev  | 
Pages: 1 2 3
Prev: Extended deadline (15 July 2010): CACS Singapore [EI Compendex,ISTP,IEEE Xplore]
Next: ARP cache size increase: how to find if this is necessary?