From mboxrd@z Thu Jan  1 00:00:00 1970
Authentication-Results: mail.toke.dk; spf=pass smtp.mailfrom=lang.hm; dkim=fail; arc=none (Message is not ARC signed); dmarc=none
Received: from mail.lang.hm (wsip-70-167-213-146.ph.ph.cox.net [70.167.213.146])
	by mail.toke.dk (Postfix) with ESMTPS id 53F6F70F832
	for <cake@lists.bufferbloat.net>; Tue, 30 Sep 2025 14:55:49 +0200 (CEST)
Received: from [10.2.2.53] (unknown [10.2.2.53])
	by mail.lang.hm (Postfix) with ESMTP id 9CC3C20AAC6;
	Tue, 30 Sep 2025 05:55:48 -0700 (PDT)
Date: Tue, 30 Sep 2025 05:55:43 -0700 (PDT)
From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
cc: Sebastian Moeller <moeller0@gmx.de>,
    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>
In-Reply-To: <D0B5EA4D-B238-44F5-93BB-2CD4E6D1CBB8@gmail.com>
Message-ID: <o99s08p9-3n8s-3229-9348-914qqo7n3929@ynat.uz>
References: <alpine.DEB.2.02.2509280400350.14652@nftneq.ynat.uz> <2064666241.42029.1759061544846@app.mailbox.org> <alpine.DEB.2.02.2509280523210.14652@nftneq.ynat.uz> <CAJUtOOj-FfPic8FPjy-QneCsvbtwtn4Zsxs+1yEsUqytEOEheg@mail.gmail.com>
 <CANypexTvXAdY577pxorqCKL45av3gw+fdupO6xr+gN5p=Wxq=Q@mail.gmail.com> <962896BA-6EE5-4815-B6F9-AC50B7252642@gmail.com> <C48271F4-4ADF-4FCA-ADA8-72C4B74D1091@gmx.de> <D0B5EA4D-B238-44F5-93BB-2CD4E6D1CBB8@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID-Hash: OJ564JRCJVOKOZ265Y3JTYTEXKX2ZSXF
X-Message-ID-Hash: OJ564JRCJVOKOZ265Y3JTYTEXKX2ZSXF
X-MailFrom: david@lang.hm
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Cake] Re: help request for cake on a large network
List-Id: Cake - FQ_codel the next generation <cake.lists.bufferbloat.net>
Archived-At: <https://lists.bufferbloat.net/cake/o99s08p9-3n8s-3229-9348-914qqo7n3929@ynat.uz/>
List-Archive: <https://lists.bufferbloat.net/cake/>
List-Help: <mailto:cake-request@lists.bufferbloat.net?subject=help>
List-Owner: <mailto:cake-owner@lists.bufferbloat.net>
List-Post: <mailto:cake@lists.bufferbloat.net>
List-Subscribe: <mailto:cake-join@lists.bufferbloat.net>
List-Unsubscribe: <mailto:cake-leave@lists.bufferbloat.net>

Jonathan Morton wrote:

>> 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.

Yep, but that means that figring out what stats we want to gather this year, in 
order to analyze over the next 12 months to configure things for next year is 
very important.

We start plugging everything in on monday, on Wednesday night, the registration 
desk is opened, and the network is now production. The first significant load is 
Thursday morning when the classes start.

David Lang