republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
20507
Share Topic
Posting?
Post a:
Post a:
Links: ·The ATM FAQ (Kool-Aid time) ·Mac Tweaks ·For New Mac Users ·The Permanent Greeting ·RC5
page: 1 · 2 · 3
AuthorAll Replies


justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

3g iphone wifi speed

I've got two iphones in front of me, 1.1.4 and 2.0 (3g). Both connect to the same home wifi network.

When I put my sim into the old phone, and try
»i.dslr.net/tinyspeedtest.html

and press the WIFI button (which triggers a larger payload), the 2g phone gets me a speed of between 1mbit and 2mbit. The test completes inside 45 seconds. A bit slow, yes, but not too bad..

When I put the same sim into the brand new 2.0 phone, (also on wifi) and do the same thing, the speed test limps along and either fails completely or sometimes gets as far as reporting a very slow speed.. 200kbit or so..

Can anyone else with a 3G iphone confirm that? and if you have a 2g iphone, verify that the "wifi" link works ok and reports a decent speed (not as fast as a PC, but ok).


justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

1 edit

I have the same problem with this 3g phone on
»testmyiphone.com

it reported a speed of 252 kbps for my wifi connected 3g iphone, yet my wifi connected laptop and mac and old iphone both tested at megabits.


Daemon
Premium
join:2003-06-29
San Francisco, CA

1 edit

reply to justin
I just pulled 2442 on my wifi network here using the dslr.net test, iPhone 2.0 build 45, 3G
--
-Ryan
sig for sale! Only one previous owner, lovingly cared for



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

said by Daemon:

I just pulled 2442 on my wifi network here using the dslr.net test, iPhone 2.0 build 45, 3G
I've tried almost everything no go..

standing right next to the (apple) airport - no difference.

turning off 3g - no difference (although signal strength on the phone side goes from 1 bar to full bars!)

testing loading the PC amazon home page over wifi - over a minute, vs instant for my wifi connected laptop and mac..

swapping sim card back and forth - 2g iphone consistently behaves as expected over wifi, 3g iphone does not.

I think I got a lemon

Daemon
Premium
join:2003-06-29
San Francisco, CA
Reviews:
·Comcast

1 edit

reply to justin
you can try changing the channel and/or 801.b compatibility settings. We have two routers here, one an apple 802.11n airport, and one an 802.11g airport express. I'm not sure which router I'm connected to at any given time, since they are connected via WDS.

What router are you using?

Also, you can try resetting the iphone, by holding the lock and home keys for several seconds, or using itunes, which should download build 47.
--
-Ryan
sig for sale! Only one previous owner, lovingly cared for



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

I am wiping the phone clean (3 hour process it warns me). Will do so after I am done.

However, I am not alone with this issue:

»forums.whirlpool.net.au/forum-re···=1015942



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

1 edit

reply to justin
I think I may have a handle on the issue..
my iphone 3g is having trouble with high latency transfers.

This US image
»nyquil.org/uploads/IndianHeadTes···16x9.png
is 250ms away for me and loads very slowly on the iphone
(fast on the mac)

But this image, which is local to me (60ms)
»www.sportsworld-pacific.com.au/P···atch.jpg
loads very quickly on the iphone

Since the speed tests for iphones are hosted in the US, they confirm the very slow speeds.



tmpchaos
Requiescat in pace
Premium,Mod
join:2000-04-28
Hoboken, NJ

Try this: »www.howzippy.com/



enOehT
Premium
join:2003-05-17
Langhorne, PA

reply to justin

3G iPhone on WIFI


enOehT
Premium
join:2003-05-17
Langhorne, PA

reply to justin

Original iPhone on WIFI


justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

Yeah you won't see the problem I am seeing because your latency to the speed test is good, sub 100ms.

But on my latency to the speed test (or any server) I'm seeing the 3g iphone very poor in transmitting back ACKs such that the connection is treated as lossy and the throughput throttles back to 25kb/sec (a quarter what it could be).

How do you do over 3G on that test? (when the latency is higher). Do you get "3g speeds"? I'd expect not, if your phone is doing what mine is doing..



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

reply to enOehT
by the way (and I appreciate you trying this out) on your 3G phone over wifi, how fast does this image
»www.sportsworld-pacific.com.au/P···atch.jpg
load?
does it come in markedly slowly given your wifi speed, much more slowly than your PC manages it?

I'm trying to show this is a widespread problem (that US users may not notice on wifi seeing as most things are local).



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

2 edits

reply to justin
I made a video, 2g iphone on the right, 3g iphone on the left. Same Wifi network, same server (our image server), same image file. Roughly the same start time. 3g wifi speed 4x slower ... doesn't matter what US image I pick, on what server, same problem:

»www.youtube.com/watch?v=92oGshWbKGI


Here is the tcptrace of the two transmissions:

first, the good one:

./bin.tcptrace.new -G -r -l 2g.dump 
 
Ostermann's tcptrace -- version 6.6.7 -- Thu Nov  4, 2004
 
1823 packets seen, 1823 TCP packets traced
elapsed wallclock time: 0:00:00.139788, 13041 pkts/sec analyzed
trace file elapsed time: 0:00:18.973276
TCP connection info:
1 TCP connection traced:
TCP connection 1:
        host a:        CPE-121-216-114-115.nsw.bigpond.net.au:61595
        host b:        nfs2:80
        complete conn: no       (SYNs: 2)  (FINs: 0)
        first packet:  Fri Jul 18 06:24:43.977745 2008
        last packet:   Fri Jul 18 06:25:02.951021 2008
        elapsed time:  0:00:18.973276
        total packets: 1823
        filename:      2g.dump
   a->b:                              b->a:
     total packets:           445           total packets:          1378      
     ack pkts sent:           444           ack pkts sent:          1378      
     pure acks sent:          443           pure acks sent:            1      
     sack pkts sent:           34           sack pkts sent:            0      
     dsack pkts sent:           0           dsack pkts sent:           0      
     max sack blks/ack:         2           max sack blks/ack:         0      
     unique bytes sent:       396           unique bytes sent:   1986504      
     actual data pkts:          1           actual data pkts:       1376      
     actual data bytes:       396           actual data bytes:   1992296      
     rexmt data pkts:           0           rexmt data pkts:           4      
     rexmt data bytes:          0           rexmt data bytes:       5792      
     zwnd probe pkts:           0           zwnd probe pkts:           0      
     zwnd probe bytes:          0           zwnd probe bytes:          0      
     outoforder pkts:           0           outoforder pkts:           0      
     pushed data pkts:          1           pushed data pkts:         97      
     SYN/FIN pkts sent:       1/0           SYN/FIN pkts sent:       1/0      
     req 1323 ws/ts:          Y/Y           req 1323 ws/ts:          Y/Y      
     adv wind scale:            0           adv wind scale:            2      
     req sack:                  Y           req sack:                  Y      
     sacks sent:               34           sacks sent:                0      
     urgent data pkts:          0 pkts      urgent data pkts:          0 pkts 
     urgent data bytes:         0 bytes     urgent data bytes:         0 bytes
     mss requested:          1460 bytes     mss requested:          1460 bytes
     max segm size:           396 bytes     max segm size:          1448 bytes
     min segm size:           396 bytes     min segm size:          1296 bytes
     avg segm size:           395 bytes     avg segm size:          1447 bytes
     max win adv:           65535 bytes     max win adv:            6864 bytes
     min win adv:            1448 bytes     min win adv:            6864 bytes
     zero win adv:              0 times     zero win adv:              0 times
     avg win adv:           56615 bytes     avg win adv:            6864 bytes
     initial window:          396 bytes     initial window:         4344 bytes
     initial window:            1 pkts      initial window:            3 pkts 
     ttl stream length:        NA           ttl stream length:        NA      
     missed data:              NA           missed data:              NA      
     truncated data:          366 bytes     truncated data:      1951016 bytes
     truncated packets:         1 pkts      truncated packets:      1376 pkts 
     data xmit time:        0.000 secs      data xmit time:       18.489 secs 
     idletime max:          700.8 ms        idletime max:          469.4 ms   
     throughput:               21 Bps       throughput:           104700 Bps  
 
     RTT samples:               2           RTT samples:             367      
     RTT min:                 0.0 ms        RTT min:               235.4 ms   
     RTT max:                 0.0 ms        RTT max:               556.1 ms   
     RTT avg:                 0.0 ms        RTT avg:               297.1 ms   
     RTT stdev:               0.0 ms        RTT stdev:              63.1 ms   
 
     RTT from 3WHS:           0.0 ms        RTT from 3WHS:         235.4 ms   
 
     RTT full_sz smpls:         1           RTT full_sz smpls:       365      
     RTT full_sz min:         0.0 ms        RTT full_sz min:       237.9 ms   
     RTT full_sz max:         0.0 ms        RTT full_sz max:       556.1 ms   
     RTT full_sz avg:         0.0 ms        RTT full_sz avg:       297.5 ms   
     RTT full_sz stdev:       0.0 ms        RTT full_sz stdev:      63.2 ms   
 
     post-loss acks:            0           post-loss acks:           12      
          For the following 5 RTT statistics, only ACKs for
          multiply-transmitted segments (ambiguous ACKs) were
          considered.  Times are taken from the last instance
          of a segment.
     ambiguous acks:            0           ambiguous acks:            1      
     RTT min (last):          0.0 ms        RTT min (last):        273.3 ms   
     RTT max (last):          0.0 ms        RTT max (last):        273.3 ms   
     RTT avg (last):          0.0 ms        RTT avg (last):        273.3 ms   
     RTT sdv (last):          0.0 ms        RTT sdv (last):          0.0 ms   
     segs cum acked:            0           segs cum acked:          993      
     duplicate acks:            0           duplicate acks:           30      
     triple dupacks:            0           triple dupacks:            1      
     max # retrans:             0           max # retrans:             1      
     min retr time:           0.0 ms        min retr time:         289.1 ms   
     max retr time:           0.0 ms        max retr time:         541.0 ms   
     avg retr time:           0.0 ms        avg retr time:         361.2 ms   
     sdv retr time:           0.0 ms        sdv retr time:         120.2 ms   
 

Now the bad one

Ostermann's tcptrace -- version 6.6.7 -- Thu Nov  4, 2004
 
2119 packets seen, 2119 TCP packets traced
elapsed wallclock time: 0:00:00.156379, 13550 pkts/sec analyzed
trace file elapsed time: 0:01:18.320963
TCP connection info:
1 TCP connection traced:
TCP connection 1:
        host a:        CPE-121-216-114-115.nsw.bigpond.net.au:61589
        host b:        nfs2:80
        complete conn: no       (SYNs: 2)  (FINs: 1)
        first packet:  Fri Jul 18 06:22:50.959222 2008
        last packet:   Fri Jul 18 06:24:09.280186 2008
        elapsed time:  0:01:18.320963
        total packets: 2119
        filename:      3g.dump
   a->b:                              b->a:
     total packets:           717           total packets:          1402      
     ack pkts sent:           716           ack pkts sent:          1402      
     pure acks sent:          715           pure acks sent:            1      
     sack pkts sent:          128           sack pkts sent:            0      
     dsack pkts sent:           0           dsack pkts sent:           0      
     max sack blks/ack:         2           max sack blks/ack:         0      
     unique bytes sent:       422           unique bytes sent:   1986504      
     actual data pkts:          1           actual data pkts:       1399      
     actual data bytes:       422           actual data bytes:   2025600      
     rexmt data pkts:           0           rexmt data pkts:          27      
     rexmt data bytes:          0           rexmt data bytes:      39096      
     zwnd probe pkts:           0           zwnd probe pkts:           0      
     zwnd probe bytes:          0           zwnd probe bytes:          0      
     outoforder pkts:           0           outoforder pkts:           0      
     pushed data pkts:          1           pushed data pkts:        119      
     SYN/FIN pkts sent:       1/0           SYN/FIN pkts sent:       1/1      
     req 1323 ws/ts:          Y/Y           req 1323 ws/ts:          Y/Y      
     adv wind scale:            2           adv wind scale:            2      
     req sack:                  Y           req sack:                  Y      
     sacks sent:              128           sacks sent:                0      
     urgent data pkts:          0 pkts      urgent data pkts:          0 pkts 
     urgent data bytes:         0 bytes     urgent data bytes:         0 bytes
     mss requested:          1460 bytes     mss requested:          1460 bytes
     max segm size:           422 bytes     max segm size:          1448 bytes
     min segm size:           422 bytes     min segm size:          1296 bytes
     avg segm size:           421 bytes     avg segm size:          1447 bytes
     max win adv:          131768 bytes     max win adv:            6864 bytes
     min win adv:          107152 bytes     min win adv:            6864 bytes
     zero win adv:              0 times     zero win adv:              0 times
     avg win adv:          129236 bytes     avg win adv:            6864 bytes
     initial window:          422 bytes     initial window:         2896 bytes
     initial window:            1 pkts      initial window:            2 pkts 
     ttl stream length:        NA           ttl stream length:   1986504 bytes
     missed data:              NA           missed data:               0 bytes
     truncated data:          392 bytes     truncated data:      1983630 bytes
     truncated packets:         1 pkts      truncated packets:      1399 pkts 
     data xmit time:        0.000 secs      data xmit time:       72.087 secs 
     idletime max:         5627.0 ms        idletime max:         5661.2 ms   
     throughput:                5 Bps       throughput:            25364 Bps  
 
     RTT samples:               2           RTT samples:             552      
     RTT min:                 0.0 ms        RTT min:               237.2 ms   
     RTT max:                 0.0 ms        RTT max:               999.4 ms   
     RTT avg:                 0.0 ms        RTT avg:               444.9 ms   
     RTT stdev:               0.0 ms        RTT stdev:             211.8 ms   
 
     RTT from 3WHS:           0.0 ms        RTT from 3WHS:         291.1 ms   
 
     RTT full_sz smpls:         1           RTT full_sz smpls:       549      
     RTT full_sz min:         0.0 ms        RTT full_sz min:       237.2 ms   
     RTT full_sz max:         0.0 ms        RTT full_sz max:       999.4 ms   
     RTT full_sz avg:         0.0 ms        RTT full_sz avg:       445.7 ms   
     RTT full_sz stdev:       0.0 ms        RTT full_sz stdev:     212.1 ms   
 
     post-loss acks:            0           post-loss acks:           31      
          For the following 5 RTT statistics, only ACKs for
          multiply-transmitted segments (ambiguous ACKs) were
          considered.  Times are taken from the last instance
          of a segment.
     ambiguous acks:            0           ambiguous acks:           15      
     RTT min (last):          0.0 ms        RTT min (last):         85.6 ms   
     RTT max (last):          0.0 ms        RTT max (last):        720.2 ms   
     RTT avg (last):          0.0 ms        RTT avg (last):        305.6 ms   
     RTT sdv (last):          0.0 ms        RTT sdv (last):        130.8 ms   
     segs cum acked:            0           segs cum acked:          776      
     duplicate acks:            1           duplicate acks:          115      
     triple dupacks:            0           triple dupacks:           11      
     max # retrans:             0           max # retrans:             1      
     min retr time:           0.0 ms        min retr time:         557.4 ms   
     max retr time:           0.0 ms        max retr time:        1229.9 ms   
     avg retr time:           0.0 ms        avg retr time:         754.5 ms   
     sdv retr time:           0.0 ms        sdv retr time:         211.8 ms   
 

The problem is visible in these details: highly variable RTT time for the 3G phone leads to stalls & congestion avoidance (slowdowns). It isn't sending back ACKs fast enough.

Daemon
Premium
join:2003-06-29
San Francisco, CA
Reviews:
·Comcast

reply to justin

said by justin:

by the way (and I appreciate you trying this out) on your 3G phone over wifi, how fast does this image
»www.sportsworld-pacific.com.au/P···atch.jpg
load?
does it come in markedly slowly given your wifi speed, much more slowly than your PC manages it?
If I watch the download progress bar, it moves as fast on Safari 3.0 in 10.5.4 as it does on my 3G phone, over wifi. The image opens slightly slower though, because downloading gets paused for sub-second periods to wait for the phone to render what's been downloaded.

But much slower? Definitely not.

macaholic
Premium
join:2003-08-31
Jackson Heights, NY

reply to justin
if you send this info to Apple maybe the fix will be included the next software update for the iPhone that brings it out of the beta program (i.e. rush this out fix it later).

Like I've been told by so many here..it's probably your internet provider's implementation of routing. Maybe you can get your provider to update their hardware so the 3g can work properly.
--
"You don't subject minority rights to a referendum." Justice Minister Irwin Cotler of Canada



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

reply to Daemon
How fast? Because here on my 3g wifi it loads in two seconds and appears during that in two or three chunks and it's done..
I added a ?nnnn random number to make sure I wasn't seeing it load from the cache..
How long for you in the us, roughly?



justin
Australian
join:1999-05-28
New York, NY
kudos:7
Host:
IPv6
Business Connectiv..
Console/Handheld g..
Console Tech
Home/Office setup ..

reply to macaholic

said by macaholic:

if you send this info to Apple maybe the fix will be included the next software update for the iPhone that brings it out of the beta program (i.e. rush this out fix it later).

Like I've been told by so many here..it's probably your internet provider's implementation of routing. Maybe you can get your provider to update their hardware so the 3g can work properly.
i guess you are being sarcastic but with both phones on the same connection to the same access point to the same server, any issue with ISP is eliminated.


enOehT
Premium
join:2003-05-17
Langhorne, PA

reply to justin


speed and latency test ran just after the video
Per your request Master.



»www.youtube.com/watch?v=nZZ4wWdjjwU


enOehT
Premium
join:2003-05-17
Langhorne, PA

reply to justin

said by justin:

does it come in markedly slowly given your wifi speed, much more slowly than your PC manages it?
Yes, much slower, my MacBook Pro handles it just fine.

macaholic
Premium
join:2003-08-31
Jackson Heights, NY

perhaps they tweeked the tcp on the little bugger for edge/3g speeds and use the same settings on wifi... you would see suboptimal performance compared to a macbook for example on the same wifi network. Is the tcp tweaker application out for it yet?
--
"You don't subject minority rights to a referendum." Justice Minister Irwin Cotler of Canada


Sunday, 12-Feb 00:44:58 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online! © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics