General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: kevin@darbyshire-bryant.me.uk, gih@apnic.net,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Tue, 12 Jun 2018 10:29:50 -0400	[thread overview]
Message-ID: <CAGhGL2B1GOG09YWQN+HxjW0wL5ers6zmr6qbaURXpe_zNd6GSw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw60AqzE5dMzmz76Z2HcfN_MrEde86r+0OUjupv5V9_kyw@mail.gmail.com>

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

On Tue, Jun 12, 2018 at 2:55 AM Dave Taht <dave.taht@gmail.com> wrote:

> On Mon, Jun 11, 2018 at 10:58 PM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
> >
> >> On 11 Jun 2018, at 22:27, Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> https://ripe76.ripe.net/presentations/10-2018-05-15-bbr.pdf
> >
> > Fascinating!
> >
> > "       • BBR changes all those assumptions, and could potentially push
> many networks into sustained instability
> >
> >         • –  We cannot use the conventional network control mechanisms
> to regulate BBR flows
> >
> > • Selective packet drop just won’t create back pressure on the flow”
> >
> > And I keep on seeing questions on whether BBR understands ECN - if not….
> well I think we see the results.
>
> I think geoff goofed in his testing of BBR, starting all flows at the
> same time, thus syncing up their probing periods. Real traffic is not
> correlated this way.
> (I made the same mistake on my initial bbr testing)
>

​Beware of self synchronization...  In other situations, there have been
situations in which aggregate behavior occurs due to this phenomena.

So both synchronized and unsynchronized startup of flows under test is
actually a good idea (and watching to see if anything in the aggregate
behavior over time results in such synchronization).
                                                  - Jim

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

  parent reply	other threads:[~2018-06-12 14:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  6:55 Dave Taht
2018-06-12  7:49 ` Geoff Huston
2018-06-12 11:25   ` Dave Taht
2018-06-12 15:58   ` Bless, Roland (TM)
2018-06-12 23:02     ` Geoff Huston
2018-06-13  7:56       ` Bless, Roland (TM)
2018-06-12 22:28   ` Greg White
2018-06-12 23:04     ` Anna Brunstrom
2018-06-12 14:29 ` Jim Gettys [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-11 21:27 Dave Taht
2018-06-12  0:42 ` Toke Høiland-Jørgensen
2018-06-12  5:09   ` Matthias Tafelmeier
2018-06-12  7:36     ` Bless, Roland (TM)
2018-06-12 11:40       ` Dave Taht
2018-06-12 12:00         ` Dave Taht
2018-06-12 17:06       ` Matthias Tafelmeier
2018-06-12  5:58 ` Kevin Darbyshire-Bryant

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=CAGhGL2B1GOG09YWQN+HxjW0wL5ers6zmr6qbaURXpe_zNd6GSw@mail.gmail.com \
    --to=jg@freedesktop.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=gih@apnic.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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