Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cobalt, compared
Date: Thu, 18 Jul 2024 11:02:57 -0700	[thread overview]
Message-ID: <CAA93jw4G+gJ7AitLkmkNhjE6VnWsR_=2ByqNYJuUmr=EJYrZ9w@mail.gmail.com> (raw)
In-Reply-To: <2B93218F-F3EF-4A79-9061-A1A3AB922CE6@gmail.com>

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

Thank you. I too was puzzled but didn't take the time to delve deeper.



On Fri, Jun 14, 2024 at 4:05 AM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 14 Jun, 2024, at 2:40 am, Dave Taht via Cake <
> cake@lists.bufferbloat.net> wrote:
> >
> >
> https://www.tu-ilmenau.de/fileadmin/Bereiche/IA/vsbs/Publikationen/2024/SSK_NOMS24_AdaptiveAQM_Authors-version.pdf
>
> I don't understand their test methodology.  I mean that literally.
>
> Their results indicate queue delays in the region of one whole second.
> This is wildly different from the target delays of any of the AQMs tested.
> In fact, their results for COBALT are above the trigger for BLUE activity
> (which they also helpfully listed in their configuration table).  One
> obvious conclusion is that COBALT's lower queue delays and higher loss
> rates in their results are precisely due to relying on the BLUE component.
> But that is most certainly not the intended operating regime for COBALT -
> BLUE is provided as a failsafe, not as a primary congestion signalling
> mechanism.
>
> They state a link rate of 2Gbps, and a variety of flow rates, the highest
> of which is 10Mbps.  Even if we multiply the latter by the number of
> clients (100), the 2Gbps link is not saturated.  If there's a separate flow
> between each client-server Cartesian product, and the clients are each
> limited to a 10Mbps link with its own AQM instance, then we should expect
> AQM activity to be capable of keeping the queue delay down to about 20ms
> (5x a small number of MTUs), which is 50x better than their typical
> reported results.
>
> I can only conclude that, for whatever reason, they have constructed a
> traffic scenario (the details of which are not adequately reported in the
> paper) which induces an extreme level of congestion, which of course the
> conventional AQMs have some trouble with handling (but COBALT does better
> on, due to BLUE activity).  They then introduce their own AQMs to this
> scenario, and report that they do better on a couple of metrics (but are
> still very bad on the others).
>
> Overall, this paper does not provide any information of interest.
>
>  - Jonathan Morton



-- 
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos

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

      reply	other threads:[~2024-07-18 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 23:40 Dave Taht
2024-06-14 11:05 ` Jonathan Morton
2024-07-18 18:02   ` Dave Taht [this message]

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4G+gJ7AitLkmkNhjE6VnWsR_=2ByqNYJuUmr=EJYrZ9w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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