General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] dslreports test reports showing a lot of improvement this year
Date: Sun, 28 Apr 2019 13:51:05 +0200	[thread overview]
Message-ID: <CAA93jw7qfT0h5NKCehOXD_tmC74+DXxuOvvWWoMx_s0RCGx_fA@mail.gmail.com> (raw)

Lacking any way to get comprehensive data from the dslreports folk,
what I've been doing has been taking a screenshot of the thing
every so often, and sticking it in a presentation, and then comparing over time.

If you look at the third slide here, with data from 2018:

http://www.taht.net/~d/sch_cake_ieee_lanman2018%20(2).pdf

And then get a current report, things are really looking up!

http://www.dslreports.com/speedtest/results/bufferbloat?up=1

My problem is that I feel that the dslreports data is now seriously
over-polluted by folk that use the site to tune up their routers with
sqm/fq_codel/cake whatever, so I keep wondering what the real state O
the world is. It is pretty obvious that upload speeds have been
migrating upwards (without changing the buffer size), at least. I'm
pretty sure docsis 3.1 modems have not deployed to a huge extent, so
we're not seeing pie all that much. About the only way I can think of
to actually track the fq_codel and cake deployments would be to start
tracking ECE and ECN marks from apple gear.



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

                 reply	other threads:[~2019-04-28 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw7qfT0h5NKCehOXD_tmC74+DXxuOvvWWoMx_s0RCGx_fA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /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