Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Vincent Frentzel <vincent@frentzel.eu>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake performance optimization
Date: Mon, 23 Nov 2015 09:50:16 +0000	[thread overview]
Message-ID: <CAO2eGh2R4_SONbRQu2WMX4WR3Qdah-p6Vfr=zGkDo8tZD4szOQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7sML=cdv_eDimizuaJGeYfvopSYUxpQHtQ58HXCU_mNA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

Sounds encouraging. Just a note/thought... I am actually not running
ingress through the IFB. I set the download speed to 0 and perform egress
shaping on the lan bridge iface (br-lan). Maybe not the lightest setup, but
this gives a really high flexiblity to classify the ingress traffic (ie. I
dont have to use best effort nor trust the incoming DSCPs which are anyway
tweaked by my provider).

On x86_64 I agree with your observation, no speed problem there. But
running a 1.83 Ghz box for routing 4 devices is a tad overkill :)

I use the connmark stuff to reclass tcp streaming traffic from CS0 to AF4x
and udp traffic to EF (Netflix/Youtube and Voip respectively). I also apply
priority to DNS (AF4x), NTP (EF), SSH (AF4x) and deprioritize some traffic
to CS1. I do this in my firewall3 config and firewall.user (some of my
rules are MAC based -> chromecast, nas box, etc..). I set the mark and
connmark save it on egress, on ingress (egress of the other iface) I simply
restore the mark. In an ideal world... all apps would apply meaningful
DSCPs to their packets and this classification would not be needed. In
general, I tend to trust the DSCPs on egress and dont override them, on
ingress I squash everything.

I used to run htb + fq_codel and performance was awful, cake performs
*much* better.

[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

  reply	other threads:[~2015-11-23  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  9:07 Vincent Frentzel
2015-11-23  9:21 ` Dave Taht
2015-11-23  9:50   ` Vincent Frentzel [this message]
2015-11-23 11:16     ` Sebastian Moeller

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='CAO2eGh2R4_SONbRQu2WMX4WR3Qdah-p6Vfr=zGkDo8tZD4szOQ@mail.gmail.com' \
    --to=vincent@frentzel.eu \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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