Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <pete@eventide.io>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: David Lang <david@lang.hm>,
	Jonathan Morton <chromatix99@gmail.com>,
	cake@lists.bufferbloat.net
Subject: Re: [Cake] Pre-print of Cake paper available
Date: Thu, 26 Apr 2018 21:27:07 +0200	[thread overview]
Message-ID: <2363649C-493E-4BBA-881B-57EEE9B9D0DB@eventide.io> (raw)
In-Reply-To: <87y3hb3uae.fsf@toke.dk>


> On Apr 25, 2018, at 10:28 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Hmm, actually it looks like just compiling against the conntrack code
> adds a module dependency on conntrack. And as far as I can tell, the
> code doesn't initiate any new conntrack state if it doesn't already
> exist. So I think it's safe to turn on NAT mode by default. Will add
> that :)

nat vs nonat CPU load for flent’s rrul_be / "cpu_stats_localhost::load" on APU2:

<limit> <nonat avg cpu load> <nat avg cpu load>
10mbit  0.07  0.07
20mbit  0.09  0.09
30mbit  0.10  0.10
40mbit  0.11  0.11
50mbit  0.13  0.13
100mbit  0.19  0.20
150mbit  0.27  0.28
200mbit  0.33  0.35
250mbit  0.39  0.41
300mbit  0.44  0.45
350mbit  0.47  0.47
400mbit  0.50  0.49
450mbit  0.50  0.51
500mbit  0.53  0.52
none  0.37  0.43 (1864 mbit total up/down)

It looks like the largest impact is when there’s no rate limiting, probably when higher packet rates are reached and the relative proportion of CPU taken is greater. I suppose the backwards results (where nonat takes more CPU than nat) at 400mbit and 500mbit are just outliers. This isn’t a perfect way to measure.

I’ll leave it to you what to do with this information. Rough estimation: nat may be +2% CPU with rate limiting, and +15% without… :)


  reply	other threads:[~2018-04-26 19:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23  8:39 Toke Høiland-Jørgensen
2018-04-23  9:54 ` Jonathan Morton
2018-04-23 23:01 ` Pete Heist
2018-04-23 23:31   ` Jonathan Morton
2018-04-24  5:44     ` Pete Heist
2018-04-24  5:58       ` Jonathan Morton
2018-04-24  7:15         ` Pete Heist
2018-04-24  7:56           ` Sebastian Moeller
2018-04-24  8:45           ` Toke Høiland-Jørgensen
2018-04-24  8:57             ` Pete Heist
2018-04-25 18:44             ` David Lang
2018-04-25 20:28               ` Toke Høiland-Jørgensen
2018-04-26 19:27                 ` Pete Heist [this message]
2018-04-27 11:08                   ` Toke Høiland-Jørgensen
2018-04-27 11:20                     ` Pete Heist
2018-04-24  8:17   ` Sebastian Moeller
2018-04-24  8:47     ` Toke Høiland-Jørgensen
2018-04-24  8:50       ` Jonathan Morton
2018-04-24  9:06         ` Pete Heist
2018-04-24  9:15           ` Toke Høiland-Jørgensen
2018-04-24  9:36             ` Pete Heist
2018-04-24  9:18       ` Sebastian Moeller
2018-04-24  9:30         ` Toke Høiland-Jørgensen
2018-04-24  9:38           ` Sebastian Moeller
2018-04-24  9:44             ` Toke Høiland-Jørgensen
2018-04-24 15:08     ` John Yates
2018-04-24  8:43   ` Toke Høiland-Jørgensen

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=2363649C-493E-4BBA-881B-57EEE9B9D0DB@eventide.io \
    --to=pete@eventide.io \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=david@lang.hm \
    --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