From: Rich Brown <richb.hanover@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] General Bufferbloat Testing Document.
Date: Sat, 16 May 2015 07:43:24 -0400 [thread overview]
Message-ID: <BDC5B4B1-F48B-41C3-BC57-7300593BF157@gmail.com> (raw)
In-Reply-To: <CAGhGL2BzxO1=4705FEkZ74RjKLW-5J5DpBiSuwG2iySX1TLy0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]
Hi Jim,
I'm glad you've got this letter going. I have started to write (mentally) this note several times, but two things always checked my momentum:
- Last summer, I sent notes asking the big speed test sites simply to add a latency test. (speedtest.net, testmy.net, speedof.me). All three responded that (basically) they would ask their developers about it, and you can see the (non) results.
- I'm afraid that it's not in their self-interest to add a latency test. Especially Ookla - I see their test package bundled as part of the offering for lots of ISPs. Ookla are hardly going to "enhance" their speed test in such a way that customer's customers can plainly see, "Congratulations on starting your service with us. You can see your speeds are pretty good, but you get an F- for bufferbloat."
The latter point is the reason that I'm so glad that Justin has added the latency test. DSLReports.com doesn't have any sacred cows to protect, so they're free to call it as it is. And I also love that they do it with a letter grade: "Hey, dude. Your connection is bloated, and you get a D".
There is still a long row to hoe, but as more and more people get de-bloated, the test will help spread around the knowledge that "it doesn't have to be that way".
Rich
On May 15, 2015, at 12:16 PM, Jim Gettys <jg@freedesktop.org> wrote:
> Even before I knew about the wonderful DSLreports bufferbloat test, I had started working on a document to help people like that (e.g. Ookla) understand how to do bufferbloat testing. The document also grew a bit beyond that topic, by the time it was done....
>
> The document is at:
>
> https://docs.google.com/document/d/1z5NN4WRKQKK-RtxtKR__XIwkybvsKEmunek2Ezdw_90/edit?usp=sharing
>
> Comments welcome.
>
> It's intended long term home is the bufferbloat.net wiki, but I've found Google doc's commenting feature really useful.
> - Jim
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Type: text/html, Size: 3504 bytes --]
next prev parent reply other threads:[~2015-05-16 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 16:16 Jim Gettys
2015-05-16 0:17 ` Stephen Hemminger
2015-05-16 8:55 ` Alan Jenkins
2015-05-16 11:43 ` Rich Brown [this message]
2015-05-18 1:58 ` Jim Gettys
2015-05-18 11:34 ` Rich Brown
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=BDC5B4B1-F48B-41C3-BC57-7300593BF157@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/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