Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] a little bit of cake testing
Date: Thu, 4 Jun 2015 11:11:04 -0700	[thread overview]
Message-ID: <CAA93jw7D1q2it1rvXRMR+PP5mOzAGUxQqA_pt_K1xWxLMxQL4Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7oGdRYF-pb=-hgq0MKG9_7KMT80cFXsMSwqVXWJwMDsQ@mail.gmail.com>

not very well controlled dataset at:
http://snapon.lab.bufferbloat.net/~d/fishcake/

On Thu, Jun 4, 2015 at 11:10 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I did a bit of setup on my connection to give me a decent rrul result.
> (I was not rate limiting inbound enough) The duration of the initial
> load spike is much less pronounced than the fq_codel result. I note
> that I have offloads still on, so I imagine fq_codel is getting
> tweaked by that....
>
> but ingress gets way out of hand later on in this test. I can make an
> argument for decay (count/2) being far too aggressive. In fact, even
> count - 2 seemed too much in older testing I had done with other
> variants. I would certainly like to get a feel for when and where the
> three parts of codel are kicking in in various workloads.
>
> http://www.dslreports.com/speedtest/613646
>
> I really need to get to where I can quickly get to a blog entry on
> this stuff, and back to comprehensive, controlled testing.
>
>
>
>
>
> On Thu, Jun 4, 2015 at 10:11 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> My network here is in flux (new modem, signal strength problems, cable
>> problems) and toke's testbed is presently doing wifi work, so I did a
>> quick mod to fishcake to make it do linux 4.0 (note I am not sure if
>> this was a 4.1 or a 4.0 change) - attached. (and we lose a few cake
>> options due to me not grokking the new API)
>>
>> Cake did well on this, but the behavior at the tail end of the test
>> was disturbing:
>>
>> http://www.dslreports.com/speedtest/611312
>>
>> Need to do some work to emulate the dslreports tests.
>>
>> And it dropped  LOT more packets than fq_codel did. fq_codel marked 33
>> packets for it's result, cake marked 600 and dropped 200, for its.
>>
>> I did some rrul testing as well, but was fighting with a modem that
>> used to get 140Mbits, and now only gets 70mbits, and behaves very
>> differently overall with pfifo_fast than i had ever seen before. And
>> along the way snapon got upgraded a bit too... sigh...
>>
>> --
>> Dave Täht
>> What will it take to vastly improve wifi for everyone?
>> https://plus.google.com/u/0/explore/makewififast
>
>
>
> --
> Dave Täht
> What will it take to vastly improve wifi for everyone?
> https://plus.google.com/u/0/explore/makewififast



-- 
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  reply	other threads:[~2015-06-04 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 17:11 Dave Taht
2015-06-04 18:10 ` Dave Taht
2015-06-04 18:11   ` Dave Taht [this message]
2015-06-04 20:31     ` Jonathan Morton

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=CAA93jw7D1q2it1rvXRMR+PP5mOzAGUxQqA_pt_K1xWxLMxQL4Q@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