From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] basic cake
Date: Wed, 25 Nov 2015 18:30:40 +0100 [thread overview]
Message-ID: <CAA93jw6xLyMkbDDAQTgvvX1ZpEW8VneTXGXa1keNRYcaTeewFQ@mail.gmail.com> (raw)
In-Reply-To: <B996B79E-6E58-4656-BFE4-2A8EF9A09000@gmx.de>
On Wed, Nov 25, 2015 at 5:37 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
> On Nov 25, 2015, at 17:02 , Dave Taht <dave.taht@gmail.com> wrote:
>
>> Last night I went about removing nearly every unproven "feature" that
>> has been added to cake since july, in part to establish a baseline for
>> a performance comparison directly against sqm-scripts with
>> htb+fq_codel, on low end hardware, and in part, to be able to test
>> each newer feature
>> more fully on the testbed.
>
> Oh, shiny, want have ;) So the plan is to assess the performance cost of each of the individual features to allow a better rationale to justify keeping or rejecting specific ones? Sounds like a excellent idea.
pithy note here:
https://github.com/dtaht/bcake/commit/4b9e6035bfa0160fa3fdaddcf1722c1cf924afa9
>
>>
>> The very long list of commits is here, complete with pithy comments,
>> in the separate repo.
>>
>> https://github.com/dtaht/bcake/commits/master
>>
>> I would like it if someone using a low end home router could benchmark
>> this version of cake
>> against the mainline version.
>
> Hrmmm, for that I would need to build my own firmwares, let’s see whether I am up for that… oh, will newcake still accept all of tc-adv’s command line arguments (and simply ignore them?)
I am keeping the api for now.
I note that first up is cake besteffort flowblind 384k and cake
besteffort flowblind 1mbit, with 5ms target.
While we have established that "bad things happen", I really don't
know what they look like. We have a lot of tools
for generating traffic, but no pictures of what actually happens.
But you might want to skip this round of testing before we establish
this baseline and move on.
>
>>
>> My plan, such as it is, is to keep simplifying, and testing. I still
>> don't get the new hashing
>> API....
>>
>> This reduction effort was fruitful in that I found yet another way to
>> reuse "now"…
>
> As long as there are few enough cycles between the uses that sounds wonderful, otherwise now degrades to once ;)
>
>> fixed one bug, maybe spotted another...
>>
>> Toke has been busy with flent, which has gained a really abusive 1000
>> tcp flows test,
>
> bidirectional by any chance? Sort of the full internet simulator for home-routers?
>
>
> Best Regards
> Sebastian
>
>> and
>> the ability to parse qdisc statistics, so long as you tell flent where
>> to get them from:
>>
>>
>> --test-parameter qdisc_stats_hosts=localhost\
>> --test-parameter qdisc_stats_interfaces=$IFACE\
>>
>> http://snapon.cs.kau.se/~d/newcake/t
>>
>>
>> --
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> https://www.gofundme.com/savewifi
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>
next prev parent reply other threads:[~2015-11-25 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 16:02 Dave Taht
2015-11-25 16:37 ` Sebastian Moeller
2015-11-25 17:30 ` Dave Taht [this message]
2015-11-25 17:45 ` Sebastian Moeller
2015-11-25 17:51 ` Kevin Darbyshire-Bryant
2015-11-25 18:23 ` Dave Taht
2015-11-25 18:31 ` Kevin Darbyshire-Bryant
2015-11-25 20:08 ` 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=CAA93jw6xLyMkbDDAQTgvvX1ZpEW8VneTXGXa1keNRYcaTeewFQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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