Article View: comp.dcom.modems.cable
Article #426Re: cable guy "vapor"-izes DSL 3X cable TV troll!
From: Lawrence Baldwin
Date: Sat, 03 Feb 2001 20:07
Date: Sat, 03 Feb 2001 20:07
76 lines
4101 bytes
4101 bytes
John Navas wrote: > > > Again, this is only a concern on *asymmetric* links. Saturation of the > uplink on a *symmetric* path will not have an adverse effect on the > downlink. > Huh? Why not? All our differences (not that we NEED to agree) seem to hinge on this point, so I'll focus here for now. Assume I've got my own dedicated, 10Mbps, full-duplex link. If I saturate the upstream with 10Mbps of one-way UDP traffic (a video stream let's say), my downstream throughput potential (for a TCP session) would be severely limited, no? The returning ACKs are going to be impeded whether the bandwidth potential on the link is assymetrical or not. All that matters is whether the upstream is saturated or not?? > >Even though bandwidth between the DSLAM and aggregation router is > >assymetric (e.g. 45Mbps full-duplex), > > Typically *symmetric*. My typo, sorry. > Possible, but unlikely given typical usage patterns of far more download > than upload. But so what? Saturating the upstream will not adversely > affect the downstream on a *symmetric* link. > > >For example, if 5% (175) of the ~4000 ADSL users aggregated into a DS3 > >ran active web servers (uploading at constant 256Kbps), you'd saturate > >the upstream. > > I'd say it's typically more like 2000-3000 subscribers per DS3, with > uplink capped at 128 Kbps, so that it would take more like about 15%. > But again, so what? I don't know what others are doing, but Bellsouth ADSL is 256Kbps upstream. Oh, and BTW, EVERY single loop I've analyzed is capable of 256Kpbs, REGARDLESS of loop length. > >I'm not saying that this is extremely likely, but I > >believe the best way to quantify the probablility is to quantify: > >upstream oversubscription rate > > >I suspect that few considered the impacts of upstream saturation on ADSL > >throughput...or ADSL downstream traffic saturating the reverse channel > >of their T1 customers...hmmmmm. > > I've not seen any real evidence of a significant problem in this area -- > have you? My DSL get's slow too...impossible to know why without having backbone access. > Regardless, the issue would be the same for cable as for > ADSL. Absolutely. BTW: I'm NOT frustrated by this conversation...as always I appreciate the engaging dialog. lb. ------------------------- Lawrence Baldwin Protocol Scientist 678-624-0924 http://www.mynetwatchman.com - I'm under attack, now what?
Technical Details
Message-ID:
<3A7C64FD.D78860D4@mynetwatchman.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.tele.dk!128.230.129.106!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mailReferences:
<3A648E27.6A7029EF@erols.com> <20010116192016044.AAA95@adsl-209-204-185-87.sonic.net@john.navasgroup.com> <3A64B680.2A79F24D@erols.com> <3A76B6CA.73B36B26@mynetwatchman.com> <4OGd6.100$mW6.5202@typhoon.sonic.net> <3A776B57.C495242C@mynetwatchman.com> <R3Ld6.144$mW6.6010@typhoon.sonic.net> <3A782325.2538A5E2@mynetwatchman.com> <diEe6.142$Tf1.5347@typhoon.sonic.net> <3A7B357B.3C2C1C79@ufl.edu> <3A7C2957.6083F801@mynetwatchman.com> <ReZe6.210$Tf1.9209@typhoon.sonic.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 113850,916316de6f72ceb X-Google-Attributes: gid113850,public X-Google-Thread: 1122a6,2145df83169cbbc6 X-Google-Attributes: gid1122a6,public X-Google-Thread: f5dc1,916316de6f72ceb X-Google-Attributes: gidf5dc1,public X-Google-ArrivalTime: 2001-02-03 12:07:35 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.tele.dk!128.230.129.106!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mail Message-ID: <3A7C64FD.D78860D4@mynetwatchman.com> From: Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com> X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.dcom.modems.cable,bellsouth.net.support.adsl,comp.dcom.xdsl Subject: Re: cable guy "vapor"-izes DSL 3X cable TV troll! References: <3A648E27.6A7029EF@erols.com> <20010116192016044.AAA95@adsl-209-204-185-87.sonic.net@john.navasgroup.com> <3A64B680.2A79F24D@erols.com> <3A76B6CA.73B36B26@mynetwatchman.com> <4OGd6.100$mW6.5202@typhoon.sonic.net> <3A776B57.C495242C@mynetwatchman.com> <R3Ld6.144$mW6.6010@typhoon.sonic.net> <3A782325.2538A5E2@mynetwatchman.com> <diEe6.142$Tf1.5347@typhoon.sonic.net> <3A7B357B.3C2C1C79@ufl.edu> <3A7C2957.6083F801@mynetwatchman.com> <ReZe6.210$Tf1.9209@typhoon.sonic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 76 Date: Sat, 03 Feb 2001 15:07:25 -0500 NNTP-Posting-Host: 208.61.191.103 X-Trace: news1.atl 981230846 208.61.191.103 (Sat, 03 Feb 2001 15:07:26 EST) NNTP-Posting-Date: Sat, 03 Feb 2001 15:07:26 EST