From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Rich Brown <richb.hanover@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
"Klatsky, Carl" <Carl_Klatsky@cable.comcast.com>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] Comcast's NANOG slides re Bufferbloat posted (Oct 2016)
Date: Thu, 20 Oct 2016 11:29:11 -0700 [thread overview]
Message-ID: <CAA93jw7vBqp0Mx=DA7FdWBEPAC16FVzsvy7kE8hKBuZcCYLSuA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1610202009400.12036@uplift.swm.pp.se>
On Thu, Oct 20, 2016 at 11:12 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Thu, 20 Oct 2016, Rich Brown wrote:
>
>>
>> https://www.nanog.org/sites/default/files/20160922_Klatsky_First_Steps_In_v1.pdf
>
>
> Does anyone understand what access speeds these customers had during these
> tests?
What that work showed was that basically all cablemodems had a fixed
upstream buffersize that is too large by factors of 25% to a factor of
10, and that 48Kbytes was a pretty good basic sweet spot... and if
they could just fix that across what's deployed life would get better
for everybody without fancy schmancy aqms... But we knew that
already....
http://www.dslreports.com/speedtest/results/bufferbloat?up=1
I note that I was called into consult a bit on this project and don't
feel at liberty at the moment to disclose their up/down parameters or
the direction of future work. Carl's nanog talk was filmed and there
were some interesting discussion afterwards about things like BBR.
https://www.youtube.com/watch?v=cA8FPHr8h7U&list=PLO8DR5ZGla8hcpeEDSBNPE5OrZf70iXZg&index=16
I was delighted that they used flent to exercise the connection(s).
> 96 kilobyte buffer on 1 megabit/s upstream or 50 megabit/s upstream makes a
> big difference.
>
> (I have 250/50 on my DOCSIS3.0 connection, but perhaps it's common knowledge
> what speeds Comcast customers typically has, that I don't know?)
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
prev parent reply other threads:[~2016-10-20 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 12:15 [Make-wifi-fast] " Rich Brown
2016-10-20 14:44 ` [Make-wifi-fast] [Cerowrt-devel] " Neal Cardwell
2016-10-20 18:12 ` Mikael Abrahamsson
2016-10-20 18:17 ` [Make-wifi-fast] [Bloat] " Klatsky, Carl
2016-10-20 21:41 ` Aaron Wood
2016-10-20 18:29 ` Dave Taht [this message]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7vBqp0Mx=DA7FdWBEPAC16FVzsvy7kE8hKBuZcCYLSuA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=Carl_Klatsky@cable.comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
--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