From: David Lang <david@lang.hm>
To: Ayush Mishra <ayumishra.95@gmail.com>
Cc: Neal Cardwell <ncardwell@google.com>,
BBR Development <bbr-dev@googlegroups.com>,
ayush@comp.nus.edu.sg, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [bbr-dev] Re: Are we heading towards a BBR-dominant Internet?
Date: Sun, 2 Apr 2023 21:27:15 -0700 (PDT) [thread overview]
Message-ID: <r41qrqpo-18s9-rpss-r4p7-1360427oo1op@ynat.uz> (raw)
In-Reply-To: <CAPGc95eEiWfBB3KKShTD2vrZVjxycYL85_58wbXi1FMXN0q=Pw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Mon, 3 Apr 2023, Ayush Mishra via Bloat wrote:
> ==> I agree too. But I think one of the key challenges here could be when
> the dynamically entering flows are extremely tiny (which I imagine is quite
> common). In those cases, there is a possibility that by the time the
> long-running flow backs off, the congestion it was responding to has
> already ended because the tiny flows have exited the bottleneck (think
> microbursts caused by flows that last 1-2 RTTs). In a perfect world we'd
> like to deal with elephant and mice flows in isolation at the switch, but
> there are likely things we can do from the endpoint too. Maybe some kind of
> a two-phase backoff, with the second phase only kicking in after a period
> of hysteresis to make sure it's responding to persistent congestion and not
> just brief microbursts. This is just off the top of my head, so I'm not
> sure how something like this would play out in the overall dynamics and
> convergence of the algorithm that implements it.
if the backoff is less drastic than currently, I would say that it's reasonable
to have the elephant back off for congestion caused by a microburst, as such
bursts are not uncommon, and while the one that triggered the backoff may finish
before the backoff happens, it's made room for the next one.
David Lang
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2023-04-03 4:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 0:01 [Bloat] " Dave Taht
2022-08-26 13:36 ` Neal Cardwell
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 [this message]
[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=r41qrqpo-18s9-rpss-r4p7-1360427oo1op@ynat.uz \
--to=david@lang.hm \
--cc=ayumishra.95@gmail.com \
--cc=ayush@comp.nus.edu.sg \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ncardwell@google.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