General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	BBR Development <bbr-dev@googlegroups.com>
Cc: kunze@comsys.rwth-aachen.de, rueth@comsys.rwth-aachen.de,
	 hohlfeld@comsys.rwth-aachen.de
Subject: [Bloat] An Empirical View on Content Provider Fairness
Date: Sun, 26 May 2019 05:07:34 -0700	[thread overview]
Message-ID: <CAA93jw4tiiGQzVznS+z6xgy5ob43M5bmUDTynJbaEFx4uNYrWA@mail.gmail.com> (raw)

re: https://arxiv.org/pdf/1905.07152.pdf

A nit with this paper is that I'd have preferred they measured and
reported the actual rtts to the CDNs they tested, rather than inflate
them 50ms via netem.

They report all sorts of different behaviors on competing flows vs a
vs akamai, cloudflare, edgecast, fastly, and google - big buffers,
small, bbr vs cubic, etc.

And, ok, ok, the final bit here after that eval happened is why I'm
reposting widely.

"Luckily, the flow-queuing variant of fq_codel enables a large degree
of fairness even in heterogeneous settings. Thus, it seems to again
stand that the technologies to enable a fair and performant Internet
are available and only need to be deployed at the bottlenecks."

Their prior work, categorizing IW sizes and behaviors in the real
world, was also quite good.

https://tma.ifip.org/2018/wp-content/uploads/sites/3/2018/06/tma2018_paper13.pdf
--

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

                 reply	other threads:[~2019-05-26 12:07 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=CAA93jw4tiiGQzVznS+z6xgy5ob43M5bmUDTynJbaEFx4uNYrWA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=hohlfeld@comsys.rwth-aachen.de \
    --cc=kunze@comsys.rwth-aachen.de \
    --cc=rueth@comsys.rwth-aachen.de \
    /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