From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 6AD4B3B2A4 for ; Wed, 25 Mar 2020 04:58:47 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1585126726; bh=U8FF1eOcZVKki1nX05CR/TvVpxozmNiPN3cn8w6YbKU=; h=From:To:Subject:In-Reply-To:References:Date:From; b=hpsjHU5NCiN/6+JiOiIIV6WDKajED3BNSxO2hvrv3X5WScEN1oxw72vxvVL0hZapT MFtiQ1NQGJi5VwIZAKUYoc9SMuzk6bb4SzKqZrRISgrcoUG1hkcA7bWyehaB1k4j9w aI/zVptQqLKuEfcGeVVDk2Den49eVq7GtpT02qcskvCymkxE7rDpGrRDubAIRCIBQv srH8q//ewRdVrHwTbGuusvx5UL1qyAL4IVrvDyjZQ4sVJwqlDvNX5a2xyR34tyNU/K tTnyRQwb2rCnWktjStpeTM6mS8mlhOXBnhlUrK3AXRbXWkYUbPTGwF5xLahajn/Aau vaDpGEx4QjU3A== To: Aaron Wood , bloat In-Reply-To: References: Date: Wed, 25 Mar 2020 09:58:46 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <875zesret5.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem 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: Wed, 25 Mar 2020 08:58:47 -0000 Aaron Wood writes: > I recently upgraded service from 150up, 10dn Mbps to xfinity's gigabit > (with 35Mbps up) tier, and picked up a DOCSIS 3.1 modem to go with it. > > Flent test results are here: > https://burntchrome.blogspot.com/2020/03/bufferbloat-with-comcast-gigabit-with.html > > tl/dr; 1000ms of upstream bufferbloat > > But it's DOCSIS 3.1, so why isn't PIE working? Theory: It's in DOCSIS 3.0 > upstream mode based on the status LEDs. Hopefully it will go away if I can > convince it to run in DOCSIS 3.1 mode. I think that while PIE is "mandatory to implement" in DOCSIS 3.1, the ISP still has to turn it on? So maybe yelling at them will work? (ha!) > At the moment, however, my WRT1900AC isn't up to the task of dealing with > these sorts of downstream rates. > > So I'm looking at the apu2, which from this post: > https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-openvpn/44724 > > Will certainly get most of the way there. My Turris Omnia is doing fine on my 1Gbps connection (although that hardly suffers from bloat, so I'm not doing any shaping; did try it though, and it has no problem with running CAKE at 1Gbps). -Toke