Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake memory usage after 1TB
Date: Thu, 24 Jun 2021 08:25:53 -0700	[thread overview]
Message-ID: <CAA93jw4TgVfM=-z74qAsj91p8k_=r4-FWjxkgpH63F9grskeeg@mail.gmail.com> (raw)
In-Reply-To: <87bl7vmgq3.fsf@toke.dk>

extremely interested in ack-filtering results both ways.

On Thu, Jun 24, 2021 at 8:21 AM Toke Høiland-Jørgensen via Cake
<cake@lists.bufferbloat.net> wrote:
>
> Sebastian Moeller <moeller0@gmx.de> writes:
>
> >> On Jun 24, 2021, at 15:59, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> >>
> >> Pete Heist <pete@heistp.net> 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.
> >
> >       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
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

      reply	other threads:[~2021-06-24 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 13:06 Pete Heist
2021-06-24 13:26 ` Pete Heist
2021-06-24 13:33   ` Dave Taht
2021-06-24 13:59 ` Toke Høiland-Jørgensen
2021-06-24 15:00   ` Pete Heist
2021-06-24 15:07   ` Sebastian Moeller
2021-06-24 15:20     ` Toke Høiland-Jørgensen
2021-06-24 15:25       ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4TgVfM=-z74qAsj91p8k_=r4-FWjxkgpH63F9grskeeg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox