From: Stephen Hemminger <stephen@networkplumber.org>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] General Bufferbloat Testing Document.
Date: Fri, 15 May 2015 17:17:57 -0700 [thread overview]
Message-ID: <20150515171757.0536e589@urahara> (raw)
In-Reply-To: <CAGhGL2BzxO1=4705FEkZ74RjKLW-5J5DpBiSuwG2iySX1TLy0w@mail.gmail.com>
On Fri, 15 May 2015 12:16:56 -0400
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
Great to see, I think it does a good job of being detailed without overwhelmingly
research oriented.
What makes you believe SPDY and QUIC will be better than TCP? I know they do
pacing but if they get the rate estimation wrong or get hit by transient congestion
it could have same failing that doomed TCP Vegas.
next prev parent reply other threads:[~2015-05-16 0:18 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 [this message]
2015-05-16 8:55 ` Alan Jenkins
2015-05-16 11:43 ` Rich Brown
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=20150515171757.0536e589@urahara \
--to=stephen@networkplumber.org \
--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