From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net,
Alan Jenkins <alan.christopher.jenkins@gmail.com>,
Daniel Havey <dhavey@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] [Cake] active sensing queue management
Date: Thu, 11 Jun 2015 18:44:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1506111835430.16013@nftneq.ynat.uz> (raw)
In-Reply-To: <BBD5DB53-976C-4150-A1B7-927B521FFBD4@gmx.de>
On Thu, 11 Jun 2015, Sebastian Moeller wrote:
>
> On Jun 11, 2015, at 03:05 , Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:
>
>> On 10/06/15 21:54, Sebastian Moeller wrote:
>>
>> One solution would be if ISPs made sure upload is 100% provisioned. Could be
>> cheaper than for (the higher rate) download.
>
> Not going to happen, in my opinion, as economically unfeasible for a
> publicly traded ISP. I would settle for that approach as long as the ISP is
> willing to fix its provisioning so that oversubscription episodes are
> reasonable rare, though.
not going to happen on any network, publicly traded or not.
The question is not "can the theoretical max of all downstream devices exceed
the upstream bandwidth" because that answer is going to be "yes" for every
network built, LAN or WAN, but rather "does the demand in practice of the
combined downstream devices exceed the upstream bandwidth for long enough to be
a problem"
it's not even a matter of what percentage are they oversubscribed.
someone with 100 1.5Mb DSL lines downstream and a 50Mb upstream (30% of
theoretical requirements) is probably a lot worse than someone with 100 1G lines
downstream and a 10G upstream (10% of theoretical requirements) because it's far
less likely that the users of the 1G lines are actually going to saturate them
(let alone simultaniously for a noticable timeframe), while it's very likely
that the users of the 1.5M DSL lines are going to saturate their lines for
extended timeframes.
The problem shows up when either usage changes rapidly, or the network operator
is not keeping up with required upgrades as gradual usage changes happen
(including when they are prevented from upgrading because a peer won't
cooperate)
As for the "100% provisioning" ideal, think through the theoretical aggregate
and realize that before you get past very many layers, you get to a bandwidh
requirement that it's not technically possible to provide.
David Lang
next prev parent reply other threads:[~2015-06-12 1:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:53 [Cerowrt-devel] " Dave Taht
2015-06-10 20:54 ` [Cerowrt-devel] [Cake] " Sebastian Moeller
2015-06-11 0:10 ` Daniel Havey
2015-06-11 7:27 ` Sebastian Moeller
2015-06-12 15:02 ` Daniel Havey
2015-06-12 16:02 ` Sebastian Moeller
2015-06-12 1:49 ` David Lang
2015-06-12 14:44 ` Daniel Havey
2015-06-13 4:00 ` David Lang
2015-06-13 5:50 ` Benjamin Cronce
2015-06-11 1:05 ` Alan Jenkins
2015-06-11 7:58 ` Sebastian Moeller
2015-06-12 1:44 ` David Lang [this message]
2015-06-12 9:52 ` [Cerowrt-devel] [Bloat] " MUSCARIELLO Luca IMT/OLN
2015-06-12 16:51 ` Benjamin Cronce
2015-06-13 4:16 ` David Lang
2015-06-12 12:18 ` Sebastian Moeller
2015-06-12 13:00 ` Alan Jenkins
2015-06-12 14:35 ` Daniel Havey
2015-06-12 17:55 ` Alan Jenkins
2015-06-13 4:34 ` David Lang
2015-06-13 4:30 ` David Lang
2015-06-13 5:37 ` [Cerowrt-devel] [Cake] [Bloat] " Benjamin Cronce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1506111835430.16013@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=alan.christopher.jenkins@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dhavey@gmail.com \
--cc=moeller0@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox