Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: dave seddon <dave.seddon.ca@gmail.com>,
	David Lang <david@lang.hm>,
	m@jaap.pro,
	"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
	Frantisek Borsik <frantisek.borsik@gmail.com>
Subject: [Cake] Re: help request for cake on a large network
Date: Tue, 30 Sep 2025 11:59:32 +0300	[thread overview]
Message-ID: <D0B5EA4D-B238-44F5-93BB-2CD4E6D1CBB8@gmail.com> (raw)
In-Reply-To: <C48271F4-4ADF-4FCA-ADA8-72C4B74D1091@gmx.de>

> On 30 Sep, 2025, at 9:09 am, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> I would really like to see some tc -s qdisc output from this network under load, as that should be informative if any twaeks are necessary at all.

I think the point is that this is a conference/event network that will be set up transiently.  By the time you get a realistic workload to measure the behaviour of, you're in production.

 - Jonathan Morton

  reply	other threads:[~2025-09-30  8:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 11:06 [Cake] " David Lang
2025-09-28 12:10 ` [Cake] " Sebastian Moeller
2025-09-28 12:17   ` David Lang
2025-09-30  9:04     ` Toke Høiland-Jørgensen
     [not found]       ` <837EA4ED-26D3-4D83-84D9-5C0C75CFB80D@gmx.de>
2025-09-30  9:23         ` Toke Høiland-Jørgensen
2025-09-28 12:12 ` Jaap de Vos
2025-09-28 12:38   ` David Lang
2025-09-28 12:56     ` Frantisek Borsik
2025-09-28 17:07       ` dave seddon
2025-09-28 17:26         ` David Lang
2025-09-30  5:18         ` Jonathan Morton
2025-09-30  6:09           ` Sebastian Moeller
2025-09-30  8:59             ` Jonathan Morton [this message]
2025-09-30  9:00               ` Sebastian Moeller
2025-09-30  3:55 ` Jonathan Morton
2025-09-30  4:30   ` dave seddon

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=D0B5EA4D-B238-44F5-93BB-2CD4E6D1CBB8@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.seddon.ca@gmail.com \
    --cc=david@lang.hm \
    --cc=frantisek.borsik@gmail.com \
    --cc=m@jaap.pro \
    --cc=moeller0@gmx.de \
    /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