From: Neal Cardwell <ncardwell@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
ayush@comp.nus.edu.sg
Subject: Re: [Bloat] Are we heading towards a BBR-dominant Internet?
Date: Fri, 26 Aug 2022 09:36:29 -0400 [thread overview]
Message-ID: <CADVnQykKbnxpNcpuZATug_4VLhV1=aoTTQE2263o8HF9ye_TQg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6hUvcj+sA9x5GrYC+QxhY13tGpMp6+1VW5Nok_inV9TQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
Yes, I agree the assumptions are key here. One key aspect of this paper is
that it focuses on the steady-state behavior of bulk flows.
Once you allow for short flows (like web pages, RPCs, etc) to dynamically
enter and leave a bottleneck, the considerations become different. As is
well-known, Reno/CUBIC will starve themselves if new flows enter and cause
loss too frequently. For CUBIC, for a somewhat typical 30ms broadband path
with a flow fair share of 25 Mbit/sec, if new flows enter and cause loss
more frequently than roughly every 2 seconds then CUBIC will not be able to
utilize its fair share. For a high-speed WAN path, with 100ms RTT and fair
share of 10 Gbit/sec, if new flows enter and cause loss more frequently
than roughly every 40 seconds then CUBIC will not be able to utilize its
fair share. Basically, loss-based CC can starve itself in some
very typical kinds of dynamic scenarios that happen in the real world.
BBR is not trying to maintain a higher throughput than CUBIC in these kinds
of scenarios with steady-state bulk flows. BBR is trying to be robust to
the kinds of random packet loss that happen in the real world when there
are flows dynamically entering/leaving a bottleneck.
cheers,
neal
On Thu, Aug 25, 2022 at 8:01 PM Dave Taht via Bloat <
bloat@lists.bufferbloat.net> wrote:
> I rather enjoyed this one. I can't help but wonder what would happen
> if we plugged some different assumptions into their model.
>
> https://www.comp.nus.edu.sg/~bleong/publications/imc2022-nash.pdf
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2613 bytes --]
next prev parent reply other threads:[~2022-08-26 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 0:01 Dave Taht
2022-08-26 13:36 ` Neal Cardwell [this message]
2022-08-26 20:54 ` [Bloat] [bbr-dev] " Bob McMahon
2022-08-27 14:44 ` Neal Cardwell
2022-08-27 20:43 ` Bob McMahon
2022-08-28 18:43 ` Neal Cardwell
2022-08-28 22:39 ` Bob McMahon
2022-08-28 23:53 ` Neal Cardwell
2022-08-29 16:47 ` Bob McMahon
2022-08-29 20:07 ` Neal Cardwell
2022-08-29 22:16 ` Bob McMahon
2023-03-28 9:36 ` Ayush Mishra
2023-03-28 10:44 ` Dave Taht
2023-04-02 13:45 ` Neal Cardwell
[not found] ` <AB22E74F-7328-4AF3-8DCB-8580331E2468@gmx.de>
2023-04-02 14:02 ` Neal Cardwell
2023-04-03 1:49 ` Ayush Mishra
2023-04-03 4:27 ` David Lang
[not found] ` <0C2095E9-B9A4-42D3-B86A-852A60508D2C@gmx.de>
2023-04-03 13:41 ` Neal Cardwell
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='CADVnQykKbnxpNcpuZATug_4VLhV1=aoTTQE2263o8HF9ye_TQg@mail.gmail.com' \
--to=ncardwell@google.com \
--cc=ayush@comp.nus.edu.sg \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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