General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Benjamin Cronce <bcronce@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fixing bufferbloat in 2017
Date: Wed, 23 Nov 2016 18:40:13 +0100	[thread overview]
Message-ID: <10E26517-2678-457D-B94D-F43056232001@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1611231829220.3558@uplift.swm.pp.se>

Well,

> On Nov 23, 2016, at 18:31, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> On Wed, 23 Nov 2016, Benjamin Cronce wrote:
> 
>> If there is a simple affordable solution, say Open/DD-WRT distro based bridge that all you do is configure your up/down bandwidth and it applies Codel/fq-Codel/Cake, then all you need to do is drive up awareness. A good channel for awareness would be getting in contact with popular Twitch or YouTube gaming streamers. But I wouldn't put much effort into driving up awareness until there is a device that people can easily acquire, use, and afford. At first I was thinking of telling people to use *-WRT supporting routers, but changing the firmware on your router requires too much research, and many people care about bleeding edge features. You need something that works in tangent with whatever they are using.
> 
> If Comcast sells you 100/20 (I have no idea if this is a thing), you set your upstream on this box to 18 meg fq_codel, and then Comcast oversubscribes you so you only get 15 meg up part of the time, then you're still bloated by the modem. This is not a solution.

since Comcast will roll-out DOCSIS3.1 modems any time now, the inbuilt PIE AQM will solve the variable upstream problem relatively well, but that still does not fix the downstream. Also oversubscription/congestion is not unique on DOCSIS systems, most ISPs have somewhere some bandwidth link that is oversubscribed (e.g. the uplink connection of aDSLAM) and there the problem is the same as on cable, namely we can only control the local bottleneck. 


> 
> I don't think "buy $thing, install *WRT on it, configure it like this" is above most gamers, but I'm afraid we don't even have a working solution for someone with that kind of skillset.

	Well we have something that can solve a big part of the problem “self-induuced” congestion on the last mile, while not a solution to all latency increase under load certainly a worthwhile improvement. Or put differently this will not remedy bandwidth competition with other subscribers, but it can solve the bandwidth competition with other local users (behind the same CPE).
Maybe we need to document better the scope of what we can and can not “deliver”?

Best Regards
	Sebastian

> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2016-11-23 17:40 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25   ` Dave Taht
2016-11-22 16:38     ` Jim Gettys
2016-11-23  8:28     ` Mikael Abrahamsson
2016-11-23 11:04       ` Jonathan Morton
2016-11-23 11:59       ` Kelvin Edmison
2016-11-23 13:31         ` Pedro Tumusok
2016-11-23 14:05           ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20           ` Mikael Abrahamsson
2016-11-23 17:27             ` Benjamin Cronce
2016-11-23 17:31               ` Mikael Abrahamsson
2016-11-23 17:40                 ` Sebastian Moeller [this message]
2016-11-23 17:50                 ` Noah Causin
2016-11-23 17:56                   ` David Lang
2016-11-23 18:05                     ` Benjamin Cronce
2016-11-23 18:38                       ` David Lang
2016-11-23 19:29                         ` Benjamin Cronce
2016-11-23 19:42                           ` David Lang
2016-11-23 20:20                             ` Dave Taht
2016-11-23 17:54                 ` David Lang
2016-11-23 18:09                   ` Mikael Abrahamsson
2016-11-23 18:18                     ` Sebastian Moeller
2016-11-23 18:24                       ` Dave Taht
2016-11-23 20:39                         ` Toke Høiland-Jørgensen
2016-11-23 19:13                       ` David Lang
2016-11-23 18:17                   ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29   ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
     [not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` Rich Brown
2016-11-23 18:46   ` David Lang
2016-11-23 18:58     ` Jonathan Morton
2016-11-23 19:15       ` David Lang
2016-11-23 20:37       ` Toke Høiland-Jørgensen
     [not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` [Bloat] Fixing " Rich Brown
2016-11-27  1:53   ` Aaron Wood
2016-11-27  6:10     ` Mikael Abrahamsson
2016-11-27 21:24   ` Dave Taht
2016-11-28  2:11     ` Kathleen Nichols
2016-11-28  2:16       ` Jim Gettys
2016-11-28  6:00         ` Jan Ceuleers
2016-11-28 12:48           ` David Collier-Brown
2016-11-28 15:12             ` Dave Taht
2016-11-28 15:23               ` Wesley Eddy
2016-11-28 15:35                 ` Dave Taht
2016-11-28 16:58                   ` Stephen Hemminger
2016-11-28 17:07                     ` Dave Taht
2016-11-28 19:02                       ` Jonathan Morton
2016-11-28 17:52                     ` Kathleen Nichols
2016-11-28 15:14             ` Pedro Tumusok
2016-11-28 15:23               ` Dave Taht
2016-11-28 15:10           ` Dave Taht
2016-11-28  2:47       ` David Lang

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10E26517-2678-457D-B94D-F43056232001@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bcronce@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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