General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: John D <j.w.r.dexter@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] SQM tuning question
Date: Sat, 3 Jun 2023 14:56:26 +0100	[thread overview]
Message-ID: <CAKWkaxE-TzwopqC6xopCv5OCG=DLqf==FjcFQvYUHQhi5o-=7g@mail.gmail.com> (raw)

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

Hi,

On the website it says the following:

*CoDel is a novel “no knobs”, “just works”, “handles variable bandwidth and
RTT”, and simple AQM algorithm.*

   - *It is parameterless — no knobs are required for operators, users, or
   implementers to adjust.*
   - *It treats good queue and bad queue differently - that is, it keeps
   the delays low while permitting bursts of traffic.*
   - *It controls delay, while insensitive to round-trip delays, link
   rates, and traffic loads.*
   - *It adapts to dynamically changing link rates with no negative impact
   on utilization.*


But everywhere I have read about about hardware which implements SQM
(including the bufferbloat website) it describes the need to tune based on
actual internet connection speed.
These seem to conflict especially that "handles variable bandwidth" bit.
Have I misunderstood or do the algorithms used in modern hardware just not
provide this part typically? My connection performance is quite variable
and I'm worried about crippling SQM to the lowest speed seen.

Thanks for any help.

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

             reply	other threads:[~2023-06-03 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 13:56 John D [this message]
2023-06-03 15:44 ` Jonathan Morton
2023-06-03 16:54   ` Kenneth Porter
2023-06-04 18:48     ` Sebastian Moeller
2023-06-03 17:17   ` John D
2023-06-03 18:04     ` Aaron Wood
2023-06-04 19:55       ` Sebastian Moeller
2023-06-04 18:56     ` Sebastian Moeller

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='CAKWkaxE-TzwopqC6xopCv5OCG=DLqf==FjcFQvYUHQhi5o-=7g@mail.gmail.com' \
    --to=j.w.r.dexter@gmail.com \
    --cc=bloat@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