General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Simon Barber <simon@superduper.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Computer generated congestion control
Date: Fri, 3 Apr 2015 10:45:37 +0300	[thread overview]
Message-ID: <CAJq5cE1=CrZS5zTNNcfSQuC=yrCpvhSrurOriTbpuhAe3D-Hvg@mail.gmail.com> (raw)
In-Reply-To: <551E364D.3070006@superduper.net>

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

I think we've seen that before. The headline results are certainly
impressive. But there's a big caveat, which is in fact revealed by the
authors.

Remy works by tailoring the congestion control algorithm to the network
characteristics that it's been told about. If the actual network it's
running on matches those characteristics, then the results are good. The
more specific that information is, the better the results. But if the
network characteristics differ from the information given, the results are
bad - and the more specific the data was, the more likely a mismatch will
occur.

If we simply knew, a priori, what the delay bandwidth product was for a
given connection, we wouldn't need congestion control algorithms in the
first place, as we could simply maintain the congestion window at that
value. That need for a priori knowledge is a fundamental problem with
Remy's approach.

So while existing, hand written congestion control algorithms aren't
perfect, in practice they tend to do a competent job in difficult
circumstances, using the limited information available to them. If
anything, I'd like them to put some sane upper bound on the RTT - one
compatible with satellite links, but which would avoid flooding unmanaged
buffers to multi-minute delays. But when they get an unambiguous congestion
signal, they respond, and so they adapt to the myriad varieties of link
characteristics actually found on real networks.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 1580 bytes --]

  reply	other threads:[~2015-04-03  7:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  6:42 Simon Barber
2015-04-03  7:45 ` Jonathan Morton [this message]
2015-04-03  8:52   ` David Lang
2015-04-03  9:28     ` Jonathan Morton
2015-04-03  9:44       ` David Lang
2015-04-03 11:06         ` Jonathan Morton
2015-04-03 12:03           ` Dave Taht
2015-04-04 23:33             ` Juliusz Chroboczek

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='CAJq5cE1=CrZS5zTNNcfSQuC=yrCpvhSrurOriTbpuhAe3D-Hvg@mail.gmail.com' \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=simon@superduper.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