Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@newmedia-net.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake memory consumption
Date: Tue, 17 Sep 2019 07:10:54 +0200	[thread overview]
Message-ID: <3de7bfb5-3393-f10e-1ffa-be46b798cea4@newmedia-net.de> (raw)
In-Reply-To: <D50283B7-56E0-44D1-A026-854D794661BC@gmail.com>


Am 16.09.2019 um 16:06 schrieb Jonathan Morton:
> If you're able to log in as root, what does "tc -s qdisc | fgrep memory" tell you?
its not my device. i need to recreate his setup (of the reporter) on my 
testbed first. then i can show you the output.
>
> Cake actually does very little dynamic memory allocation.  There's a small amount of memory used per queue and per tin, which should total less than 100KB in "besteffort" mode (which you should be using if you have manual traffic classification).
bestefford is used. yes
>
> All other memory consumption is due to packets in the queue, which are allocated by the kernel when they are received, and deallocated when transmitted or dropped.  Cake applies a limit to the memory used by queued packets, generally 4MB by default.  The only way this can be exceeded by more than one packet (transiently, when a packet is enqueued and Cake has to drop other packets to make room) is if there's an unaccounted memory leak somewhere.
>
> If you can find such a leak in Cake, we'll fix it.  But I think it is probably elsewhere.

even if elsewhere i'm wondering why only cake triggers it. there is 
nothing different in between when comparing with other schedulers
i dont see a leak here. i more see a massive consumption here. i can run 
cake on devices with more memory and it will not run out of memory.
the assumption is that cake takes the 4 mb memory per qdisc and i have 
alot of  qdiscs


>
>   - Jonathan Morton

  reply	other threads:[~2019-09-17  5:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-07 22:42 [Cake] Fighting bloat in the face of uncertinty Justin Kilpatrick
2019-09-07 23:09 ` Jonathan Morton
2019-09-07 23:31   ` Justin Kilpatrick
2019-09-07 23:42     ` Jonathan Morton
2019-09-08  0:03       ` Justin Kilpatrick
2019-09-08  0:59         ` Jonathan Morton
2019-09-08 14:29           ` Justin Kilpatrick
2019-09-08 17:27             ` Jonathan Morton
2019-09-16 10:21               ` [Cake] cake memory consumption Sebastian Gottschall
2019-09-16 12:00                 ` Dave Taht
2019-09-16 12:51                   ` Dave Taht
2019-09-16 13:31                     ` Sebastian Gottschall
2019-09-16 13:22                   ` Sebastian Gottschall
2019-09-16 13:28                     ` Justin Kilpatrick
2019-09-16 13:39                       ` Jonathan Morton
2019-09-16 13:54                         ` Sebastian Gottschall
2019-09-16 14:06                           ` Jonathan Morton
2019-09-17  5:10                             ` Sebastian Gottschall [this message]
2019-09-16 13:47                       ` Sebastian Gottschall
2019-09-16 12:08                 ` Toke Høiland-Jørgensen
2019-09-16 13:25                   ` Sebastian Gottschall
2019-09-16 14:01                     ` Toke Høiland-Jørgensen
2019-09-17  5:06                       ` Sebastian Gottschall
2019-09-17  5:21                       ` Sebastian Gottschall
2019-09-17  5:31                       ` Sebastian Gottschall
2019-09-17  9:21                         ` Jonathan Morton
2019-09-17  9:55                           ` Sebastian Gottschall
2019-09-17  5:33                       ` Sebastian Gottschall
2019-09-17  9:40                         ` Toke Høiland-Jørgensen
2019-09-18  7:19                           ` Sebastian Gottschall
2019-09-18  9:53                             ` Toke Høiland-Jørgensen
2019-09-18  9:57                               ` Sebastian Gottschall
2019-09-18 10:22                                 ` Toke Høiland-Jørgensen
2019-10-03 17:52               ` [Cake] Fighting bloat in the face of uncertinty Justin Kilpatrick
2019-10-03 18:41                 ` Dave Taht
2019-10-03 19:04                 ` Jonathan Morton

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=3de7bfb5-3393-f10e-1ffa-be46b798cea4@newmedia-net.de \
    --to=s.gottschall@newmedia-net.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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