From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-h1p-028588.sys.comcast.net (resqmta-h1p-028588.sys.comcast.net [IPv6:2001:558:fd02:2446::a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DACB33B29D for ; Sat, 3 Jun 2023 12:55:43 -0400 (EDT) Received: from resomta-h1p-027908.sys.comcast.net ([96.102.179.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h1p-028588.sys.comcast.net with ESMTP id 5Tl0qdZ3idWsM5UXVq3L0d; Sat, 03 Jun 2023 16:55:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1685811341; bh=CmhBEpNSgWQkyVblbIUQ9V2UM+lRWetyLcINzqs66H0=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type:Xfinity-Spam-Result; b=UeVx2hRxFcX/jgC/6DEGJJ9A6hN6Tg+SKgZWDstSNw5wOGpFbxFzFkBJZJLfUyIsm 8fFGy2jseemBHZEZFhnnvcZdC7CXbPFJ2FaymaIFqvjBEahXzh2OHCUzTU8Pu4ZOZ9 28zmsCunYow9UsDpYrYEZKSD4vmmVTqQ2tUy7SKib+c9TVVY7xe6Aw2z3EG33dt/9w 4s6XoehjtxwCHg5tTyoDzF/hg2C5s2gtW/fpoTNqjgEZzGIkkHDJioHbfJpahoV76p gQMBRtjWmrNw6URlGzCEjq6jZjplA/IAB5CXhcPkXhZpdEG4P4SWHoo3AH7P0b1zvD GY6DBNjZZMaHQ== Received: from home.sewingwitch.com ([98.35.153.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-h1p-027908.sys.comcast.net with ESMTPA id 5UXSqHtY4Dmy55UXUq5dK8; Sat, 03 Jun 2023 16:55:41 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelhedguddtkecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkjghfofggtgfgugesthejiedtnfdtvdenucfhrhhomhepmfgvnhhnvghthhcurfhorhhtvghruceoshhhihhvrgesshgvfihinhhgfihithgthhdrtghomheqnecuggftrfgrthhtvghrnhepteevheefveefkeffiedugfevfeejtdeuvdetleetuefgvdekgfefgffhhfekkeeinecukfhppeelkedrfeehrdduheefrdduudejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohephhhomhgvrdhsvgifihhnghifihhttghhrdgtohhmpdhinhgvthepleekrdefhedrudehfedruddujedpmhgrihhlfhhrohhmpehshhhivhgrsehsvgifihhnghifihhttghhrdgtohhmpdhnsggprhgtphhtthhopedupdhrtghpthhtohepsghlohgrtheslhhishhtshdrsghufhhfvghrsghlohgrthdrnhgvth X-Xfinity-VMeta: sc=-100.00;st=legit Received: from [10.96.7.39] ([10.96.7.39]) (authenticated bits=0) by home.sewingwitch.com (8.14.7/8.14.7) with ESMTP id 353GsXR2003587 for ; Sat, 3 Jun 2023 09:54:34 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 home.sewingwitch.com 353GsXR2003587 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sewingwitch.com; s=default; t=1685811274; bh=CmhBEpNSgWQkyVblbIUQ9V2UM+lRWetyLcINzqs66H0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=zx7+DLRSb3zFXZG3Cdz1UQdysjwal5uXSbdQ+cyLfimUCspaLWWZjFNKWYX4/ER1W kwS3wsVxNjHdoXi0GTXN9ekIluN2vj9MUIKQWVP2CbO0CSjX8hHXiml3Hrk23XnZrr SUVo9gP3bzhpcCULl2vEzWiN88hRc+M+g6rJDCuQ= Date: Sat, 03 Jun 2023 09:54:34 -0700 From: Kenneth Porter To: Jonathan Morton via Bloat Message-ID: <642118391FA06B4E63C6FA57@[10.96.7.39]> In-Reply-To: <39DED14A-AACF-4C45-9834-C295F92E8800@gmail.com> References: <39DED14A-AACF-4C45-9834-C295F92E8800@gmail.com> X-Mailer: Mulberry/4.1.0a3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=846 X-Scanned-By: MIMEDefang 3.3 on 10.96.0.132 Subject: Re: [Bloat] SQM tuning question X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jun 2023 16:55:44 -0000 --On Saturday, June 03, 2023 7:44 PM +0300 Jonathan Morton via Bloat wrote: > When your available bandwidth varies over time, that can be inconvenient. > There are methods, however, of observing how available capacity tends to > change over time (typically on diurnal and weekly patterns, if the > variations are due to congestion in the ISP backhaul or peering) and > scheduling adjustments on that basis. If you have more information on > your situation, we might be able to give more detailed advice. Are there any good solutions for regularly recomputing the bandwidth on a consumer link? I'm running the Linux SQM scripts to launch cake on a recent Debian system and CoDel on a CentOS 7 gateway. I set the bandwidth manually based on periodic manual speed tests. I'd love to automate that.