NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
| reply to Selenia
Re: [Home Network] latency / lag on DSL vs. cablesaid by Selenia:I would still go with dsl if you're close to the CO. Latency and loss increase with distance... How close is "close"?
12/31/07 12:10:31 Slow traceroute www.yahoo.com
Trace www.yahoo.com (209.131.36.158) ...
192.168.102.1 RTT: 1ms TTL:170 (chihiro.aosake.net ok)
192.168.0.1 RTT: 2ms TTL:170 (suzuka.aosake.net ok)
69.110.151.254 RTT: 11ms TTL:170 (adsl-69-110-151-254.dsl.pltn13.pacbell.net ok)
64.164.107.1 RTT: 11ms TTL:170 (No rDNS)
151.164.93.231 RTT: 11ms TTL:170 (bb1-g15-0.pltnca.sbcglobal.net ok)
151.164.191.201 RTT: 11ms TTL:170 (ex1-p9-0.eqsjca.sbcglobal.net ok)
151.164.248.58 RTT: 12ms TTL:170 (asn10310-yahoo-10g.eqsjca.sbcglobal.net ok)
216.115.107.83 RTT: 12ms TTL:170 (g-0-0-0-p171.msr2.sp1.yahoo.com ok)
209.131.32.17 RTT: 12ms TTL:170 (te-8-1.bas-a1.sp1.yahoo.com ok)
209.131.36.158 RTT: 12ms TTL: 55 (f1.www.vip.sp1.yahoo.com ok)
I am 9,156 feet from my DSLAM (which is in a CO; but DSLAMs can also be in RTs).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
 pflogBueller? Bueller?Premium,MVM
join:2001-09-01
El Dorado Hills, CA
kudos:3 | Upstream sync rate on DSL results in marginally lower RTT pings to the POP. I think going from 384k upstream to 608k upstream, I saw a drop in GW ping from about 11-12ms to 7-8ms. Not a huge difference, that, but of note.
Also, in my experience, DSL pings are much more consistent and stable. Cable tends to fluctuate quite a bit, at least it has in areas I've had Cable. This, as I said, can definitely vary by Comcast market.
Here's the ping to my gateway on my parents' Comcast connection (which is actually very good):
Pinging 71.200.176.1 with 32 bytes of data:
Reply from 71.200.176.1: bytes=32 time=9ms TTL=254
Reply from 71.200.176.1: bytes=32 time=8ms TTL=254
Reply from 71.200.176.1: bytes=32 time=6ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=9ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=10ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=11ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=8ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Reply from 71.200.176.1: bytes=32 time=11ms TTL=254
Reply from 71.200.176.1: bytes=32 time=6ms TTL=254
Reply from 71.200.176.1: bytes=32 time=15ms TTL=254
Reply from 71.200.176.1: bytes=32 time=8ms TTL=254
Reply from 71.200.176.1: bytes=32 time=6ms TTL=254
Reply from 71.200.176.1: bytes=32 time=7ms TTL=254
Ping statistics for 71.200.176.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 15ms, Average = 8ms
So it's 6-8ms most of the time, but with spikes to 10+ a few times (even 15). This is actually very good, I've seen it much more jittery. On DSL, though, when I'd ping my gateway, I'd see 10ms for every reply with a std deviation of less than 0.5ms. 
--
Hello...is there anybody in there? |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| This is what I see...
Ping statistics for 69.110.151.254:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 14ms, Average = 11ms
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
 en102Canadian, eh?
join:2001-01-26
Valencia, CA | Some of that is due to location (i.e. San Jose to San Jose trace to yahoo.com)
L.A. to San Jose is a little farther
$ tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.254.11
2 10 ms 10 ms 9 ms netblock-68-183-52-1.dslextreme.com [68.183.52.1]
3 10 ms 10 ms 10 ms LAX1.CR1.Gig6-0.dslextreme.com [66.51.199.133]
4 20 ms 20 ms 20 ms netblock-66-51-198-182.dslextreme.com [66.51.198.182]
5 20 ms 20 ms 21 ms PAT2.SJC.yahoo.com [206.223.116.16]
6 21 ms 20 ms 22 ms g-1-0-0-p161.msr1.sp1.yahoo.com [216.115.107.63]
7 25 ms 22 ms 22 ms te-8-1.bas-a2.sp1.yahoo.com [209.131.32.19]
8 22 ms 21 ms 21 ms f1.www.vip.sp1.yahoo.com [209.131.36.158]
Trace complete.
--
Canada = Hollywood North |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Yeah, but how far are you from your DSLAM? It is the latency to the gateway router which is what I am looking at. My DSLAM is 9,156 out. I'd be curious to see the latency on a DSL line at 15,000 feet; especially if they were on the Fast data path.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
en102Canadian, eh?
join:2001-01-26
Valencia, CA | said by NormanS:Yeah, but how far are you from your DSLAM? It is the latency to the gateway router which is what I am looking at. My DSLAM is 9,156 out. I'd be curious to see the latency on a DSL line at 15,000 feet; especially if they were on the Fast data path. According to AT&T techs, I'm at ~12,000', and I'm on fastpath 3008/512kbps (which they no longer offer for me).
--
Canada = Hollywood North |
|
