Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
	Rich Brown <richb.hanover@gmail.com>
Cc: "make-wifi-fast@lists.bufferbloat.net"
	<make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] [Cerowrt-devel] Comcast's NANOG slides re Bufferbloat posted (Oct 2016)
Date: Thu, 20 Oct 2016 18:17:18 -0000	[thread overview]
Message-ID: <aba59098b3854671bdaf338694f43da8@PACDCEX43.cable.comcast.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1610202009400.12036@uplift.swm.pp.se>

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?
[Carl Klatsky] For this trial, the customers were provisioned with 110 Mbps down / 10 Mbps up.

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
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2016-10-20 18:17 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   ` Klatsky, Carl [this message]
2016-10-20 21:41     ` [Make-wifi-fast] [Bloat] " Aaron Wood
2016-10-20 18:29   ` [Make-wifi-fast] " Dave Taht

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=aba59098b3854671bdaf338694f43da8@PACDCEX43.cable.comcast.com \
    --to=carl_klatsky@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