Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	Jonathan Morton <chromatix99@gmail.com>,
	cake@lists.bufferbloat.net
Subject: Re: [Cake] second system syndrome
Date: Mon, 21 Dec 2015 11:40:00 +0100	[thread overview]
Message-ID: <CAA93jw6NN2vWRjuB46eL69_tQqhBvLAvA8nAeH0TyYhiU1TsyQ@mail.gmail.com> (raw)
In-Reply-To: <B1BE65C1-480C-4122-A877-5A0C7445C705@gmx.de>

On Mon, Dec 21, 2015 at 10:02 AM, moeller0 <moeller0@gmx.de> wrote:
> I had a quick look over these, both htb+fq_codel egress and bcake egress (both without perf) seem “contaminated" by a periodic process with a period of 50/8 = 6.25 seconds. Is this one of the cyclic probes measuring cpu load or so?
>         BTW are you using simplest.qos or simple.qos for the htb+fq_codel test (or something unrelated to sqm)? I ask because we have a shipload of costly iptables/tc filter stuff only happening in simple.qos (while rural_be will not use any DSCPs besides 0 the filters should still cost a bit CPU). I do not seem to be able to see any additional meta information from the flent files, probably PEBCAK n my side...

simple.qos.

see also: https://github.com/dtaht/sch_cake/commit/a66ee4fa355a62633b34fd05834075ea294e3b79

Did not switch cake over to it...

I still do not see any reason for precedence or diffserv8 to exist,
and can barely cope with the idea of diffserv4.

>
> Best Regards
>         Sebastian
>
>
>> On Dec 20, 2015, at 13:52 , Dave Taht <dave.taht@gmail.com> wrote:
>>
>> the 200/20mbit tests I ran yesterday.
>>
>> http://snapon.cs.kau.se/~d/ptests/
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>

  reply	other threads:[~2015-12-21 10:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 14:53 Dave Taht
2015-12-06 16:08 ` Sebastian Moeller
2015-12-07 12:24   ` Kevin Darbyshire-Bryant
2015-12-20 12:47     ` Dave Taht
2015-12-20 12:52       ` Dave Taht
2015-12-21  9:02         ` moeller0
2015-12-21 10:40           ` Dave Taht [this message]
2015-12-21 11:10             ` moeller0
2015-12-21 12:00               ` Dave Taht
2015-12-21 13:05                 ` moeller0
2015-12-21 15:36                   ` Jonathan Morton
2015-12-21 18:19                     ` moeller0
2015-12-21 20:36                       ` Jonathan Morton
2015-12-21 21:19                         ` moeller0
     [not found]                         ` <8737uukf7z.fsf@toke.dk>
2015-12-22 15:34                           ` Jonathan Morton
2015-12-22 22:30                     ` Kevin Darbyshire-Bryant
2015-12-23 11:43                       ` Dave Taht
2015-12-23 12:14                         ` Kevin Darbyshire-Bryant
2015-12-23 12:27                         ` Jonathan Morton
2015-12-23 12:41                           ` Dave Taht
2015-12-23 13:06                             ` Jonathan Morton
2015-12-23 14:58                               ` Dave Taht
2015-12-20 13:51       ` moeller0
2015-12-06 18:21 ` Kevin Darbyshire-Bryant

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=CAA93jw6NN2vWRjuB46eL69_tQqhBvLAvA8nAeH0TyYhiU1TsyQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=moeller0@gmx.de \
    /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