General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
Cc: "Matthias Tafelmeier" <matthias.tafelmeier@gmx.net>,
	bloat <bloat@lists.bufferbloat.net>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Tue, 12 Jun 2018 04:40:55 -0700	[thread overview]
Message-ID: <CAA93jw5d=C5q-G5CFT=TER7D1-NPJRWGoQ-KMjLKqESMCuvA5g@mail.gmail.com> (raw)
In-Reply-To: <1b46d724-6568-c4ee-9860-86ae504434a3@kit.edu>

On Tue, Jun 12, 2018 at 12:36 AM, Bless, Roland (TM)
<roland.bless@kit.edu> wrote:
> Hi,
>
> Am 12.06.2018 um 07:09 schrieb Matthias Tafelmeier:
>> On 06/12/2018 02:42 AM, Toke Høiland-Jørgensen wrote:
>>>> https://ripe76.ripe.net/presentations/10-2018-05-15-bbr.pdf
>>> "More research needed". Naturally ;)
>>>
>>> (But yeah, good points overall)
>>
>> Interesting. Potentially, all affectuated. After having applied the BBR
>> 2.0, we might are back to Cubic? :D
>
> I don't understand what you're saying. I think Geoff tested BBR v1.0.
> Explanations for the experienced behavior can be found in our paper
> http://doc.tm.kit.edu/2017-kit-icnp-bbr-authors-copy.pdf, esp. section
> 3. Geoff's findings in the wild nicely confirm our results that were
> performed in more controlled lab settings. Important is though, that
> you always test with multiple concurrent BBR flows...

we always do that, 'round here, with flent. Glad more folk are doing it. :)

>> Moreover, if it tends to be unstable on larger scale - what is Google
>> doing then? Thought they've got a more or less homogeneous BBR driven
>> TCP flow ecosystem - at least internally!? Was all propaganda? When
>> speculating, might working for them since of centrally handled flow
>> steering approaches - "imposing inter-flow fairness".
>
> There are certain situations where BBR might work well:
> 1) you only have a single flow at the bottleneck, might be the case in
> their B4 scenario
> 2) The senders a application limited (e.g., YouTube)

I think the application limited scenario is the primary one. once
typical links are fully capable of video streaming
4k video a lot of the demand for better congestion control will drop.

> 3) The bottleneck buffer is much larger than a BDP
>    (then BDP will limit the queue size between 1 and 1.5 BDP)

Sadly we still see 2sec queues on cmtses, in particular.

> However, BBR has no explicit fairness mechanism, so sometimes
> one will see quite unfair shares for longer periods,
> even if there are only BBR flows present at then bottleneck.

except with fq at the bottleneck.

>
> Regards
>  Roland
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-06-12 11:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2018-06-12 12:00         ` Dave Taht
2018-06-12 17:06       ` Matthias Tafelmeier
2018-06-12  5:58 ` Kevin Darbyshire-Bryant
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

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='CAA93jw5d=C5q-G5CFT=TER7D1-NPJRWGoQ-KMjLKqESMCuvA5g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=matthias.tafelmeier@gmx.net \
    --cc=roland.bless@kit.edu \
    --cc=toke@toke.dk \
    /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