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 BA7113B2A4 for ; Thu, 24 Jun 2021 11:21:03 -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=1624548055; bh=3NF3YSCJdiHJp7a+f9E+0BneF1SjXokapR/euXWdp8k=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=dn1Zhc7BtolFB/4ut3p/u4GiFmcO125lVAyHAnD4MfW/aM0vc/Fa45Ic+7W47zzLY swfyHq56KiukZc80csDyN5mpRq+mhhDs8VR+szMUDxI2GbK3N++jWLkTVLqPQe8TOu AAD+I78J0ATrIyt1N4T67oaJmZ2Z2Hw1i65ehY8296GnN7IYbiodCyFtjRG8aZHbGm b3VfO8tDCVR6PX6jT9pUML4/jID1Balk2TyuJGtMrxvsEhIA0RRzx7gN8TZTgp5POd hIkO8pjrabk7grMLQhkQZ9o8kYVXIcAR0BbznetC3ja7UhIa5TaLpze80jt3VfmD5m 7p1P7R7VzEd0g== To: Sebastian Moeller Cc: Pete Heist , Cake List In-Reply-To: <0341E253-B8CB-4976-ABC1-553C070E77F3@gmx.de> References: <3d529e0b78ef8ea54021d8f8e93285e9a474cba1.camel@heistp.net> <87h7hnmkhc.fsf@toke.dk> <0341E253-B8CB-4976-ABC1-553C070E77F3@gmx.de> Date: Thu, 24 Jun 2021 17:20:52 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87bl7vmgq3.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] Cake memory usage after 1TB X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2021 15:21:03 -0000 Sebastian Moeller writes: >> On Jun 24, 2021, at 15:59, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> Pete Heist writes: >>=20 >>> I'm using Cake on an EdgeRouter-X at a site that does around 50- >>> 100GB/day, and we're quite happy with it so far. Egress and ingress >>> stats are below after ~1TB download and ~100GB upload. >>>=20 >>> I use "memlimit 8M", and noticed that it's reporting 8389696 bytes used >>> on egress, which is at the maximum (slightly over actually). Around 6M >>> is used on ingress. Should I then raise these limits, or is it normal >>> for it to settle in around the maximum over time? >>=20 >> That stat is the maximum memory ever used, not the current usage (that >> is reported by "backlog 0b 0p"). So if your queue ever overflows it'll >> be at its maximum. > > Is there an easy way to reset that, short of tearing down the > qdisc set-up and building it up again? Nope, 'fraid not :) -Toke