Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] cake, mq and bql on the apu2
Date: Sat, 28 Jul 2018 09:51:21 -0700	[thread overview]
Message-ID: <CAA93jw7-=PUX+=uqJNAszH6ajEah3hpnZ_LUSDXGrUrHBxBBRw@mail.gmail.com> (raw)

so, as I gradually built up my lab over the past few weeks I slammed
ubuntu into one of my prized apu-2s to take a look at cake. This
particular box has 4 hardware queues, so I made cake the default qdisc
to see what happened at line rate. Running netserver locally on it
(which is a dumb idea, I just wanted to
see what happened) -

It works at a gbit fine, but bql stablizes at about 60-100k per queue,
(120-200 with gso enabled). I can set bql's limit_max to about 50k but
start losing single stream performance below that (bql tends to be off
by 2x in any scenario), for example, 20k for bql the best a single
flow can do is 500mbit, so there is a
lot more context switch overhead than I'd like compared to a fluid model.

running cake as the sole qdisc, unshaped, bql stablizes a little
higher, but throughput suffers (800k) also. In all cases observed
latencies are much higher that desirable due to all the extra bql
buffering, in 2-5ms range. If I shape to 100mbit, I get .36ms for ping
on workloads from 1 to 16 streams.

And also of course there's the usual birthday problem caused by so few queues.

I'm going to go setup two boxes on the other side of it next.

I've never liked bql's MIAD (rather than AIMD) scheme, I really hope
that not running the test locally will reduce the automagically sized
bql buffers smaller.

Then I'll flash lede on another one and see what happens. Any ethtool
settings for NAPI in particular worth trying?

-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

                 reply	other threads:[~2018-07-28 16:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw7-=PUX+=uqJNAszH6ajEah3hpnZ_LUSDXGrUrHBxBBRw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /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