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 C983D3B2A4 for ; Thu, 24 Jun 2021 09:59:46 -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=1624543184; bh=i0qOYnmvOe2HrEqNKXKzZRwDJ8TyXv22JRscgxrO8Ko=; h=From:To:Subject:In-Reply-To:References:Date:From; b=fgTbqs+864EZb3/+DENdGWmYfKveQEvkMJoaNspVoeDhuA9XB0yhsoSCcga7srmNV iZbbu/TkkZ5aV7DTodv/kV12XwsY3s9+FiBD9K2AIoFHje0F9dzjcQDnLS6/Nfyif1 VVK8hLsZG/o+R3KPuzsq1KyiVDIEWdqKkKVrNrbMwIc4Z+14zbAHqlicXXW2UsDfv4 uLScUhvKCZOg/y2S+lwAt/6pJHoxYJDltoTw3UbhK7fiMgKtcq9Qzj6lyiM7L/jrYn Ic1+7XtpVZ3Cv6CVeljUp8P3PZJ489LMNT2Hwbql606myh7MoD1A7Tk4x3+PYOo253 1RiCFaSFlmVdg== To: Pete Heist , Cake List In-Reply-To: <3d529e0b78ef8ea54021d8f8e93285e9a474cba1.camel@heistp.net> References: <3d529e0b78ef8ea54021d8f8e93285e9a474cba1.camel@heistp.net> Date: Thu, 24 Jun 2021 15:59:43 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87h7hnmkhc.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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 13:59:46 -0000 Pete Heist writes: > 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. > > 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? 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. -Toke