Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Kathleen Nichols <nichols@pollere.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Dissecting Starlink: head-drop queuing, AQM, and flow dynamics (SIGCOMM '26)
Date: Wed, 22 Jul 2026 06:49:18 -0700	[thread overview]
Message-ID: <cbb56513-fce2-4b19-b4b8-a31df3e19fd3@pollere.net> (raw)
In-Reply-To: <D6D70BEF-3FB6-4279-815A-817B926CAE0A@tudelft.nl>


This is interesting work, thanks. But I want to point out that, if 
indeed the "Loss frequency grows with queue occupancy" that isn't CoDel 
which increases loss frequency with a persistent sojourn delay. (A large 
point of CoDel was to get away from queue occupancy as a congestion signal.)

	Kathie

On 7/22/26 2:00 AM, Nitinder Mohan via Starlink wrote:
...
>    *   There is a real AQM that deliberately drops to control occupancy. The uplink is aggressive and holds flows below a quarter of physical capacity. The downlink is more permissive. Loss frequency grows with queue occupancy, and the load-dependent profile looks closer to CoDel or adaptive RED than fixed RED.
...


  reply	other threads:[~2026-07-22 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  9:00 [Starlink] Dissecting Starlink: head-drop queuing, AQM, and flow dynamics (SIGCOMM '26) Nitinder Mohan
2026-07-22 13:49 ` Kathleen Nichols [this message]
2026-07-22 14:26   ` [Starlink] " Nitinder Mohan
2026-07-22 15:18     ` Jianping Pan
2026-07-22 15:21       ` Nitinder Mohan
2026-07-22 15:23         ` Jianping Pan

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

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

  git send-email \
    --in-reply-to=cbb56513-fce2-4b19-b4b8-a31df3e19fd3@pollere.net \
    --to=nichols@pollere.net \
    --cc=starlink@lists.bufferbloat.net \
    /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