From: Geoff Huston <gih@apnic.net>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Wed, 13 Jun 2018 09:02:43 +1000 [thread overview]
Message-ID: <4E4AF97A-8B22-4355-AF63-B27529F22D94@apnic.net> (raw)
In-Reply-To: <a96cf764-a5aa-c79d-293b-2e3511917f8b@kit.edu>
> On 13 Jun 2018, at 1:58 am, Bless, Roland (TM) <roland.bless@kit.edu> wrote:
>>
>> no - I started the flows at 10, 20 and 30 seconds after the initial flow started.
>
> This is nevertheless advantageous for BBR, since it performs its
> ProbeRTT phase every 10s. So using 11, 23, and 34 seconds may
> make a difference in convergence speed (that was at least observed
> in our experiments).
I’m not sure that I follow this - It was my understanding that BBR used the RTT interval as its control timer, and maintained a constant send rate for 6 successive RTTY intervals, then inflated the sending r4ate by 25% for the next RTT interval and deflated it by the same amount for the next RTT interval. I don’t believe that there is any absolute timer in BBR along the lines of a 10 second timer that you appear to be suggesting here.
regards,
Geoff
next prev parent reply other threads:[~2018-06-12 23:03 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 [this message]
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
-- 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=4E4AF97A-8B22-4355-AF63-B27529F22D94@apnic.net \
--to=gih@apnic.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=roland.bless@kit.edu \
/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