Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Luis E. Garcia" <luis@bitamins.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	 "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Master branch updated
Date: Tue, 11 Oct 2016 06:09:32 -0600	[thread overview]
Message-ID: <CALnBQ5nAW6f8eWBxzAMecKPqeyFU9vLYL_qbbE7JJSEGv2Rq3g@mail.gmail.com> (raw)
In-Reply-To: <BE9B43B5-DBD2-45E8-926C-95592A7D38E8@gmail.com>

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

If we can replicate the results of your test then I would say we're onto
something.

On Monday, 10 October 2016, Jonathan Morton <chromatix99@gmail.com> wrote:

>
> > On 4 Oct, 2016, at 19:28, Jonathan Morton <chromatix99@gmail.com
> <javascript:;>> wrote:
> >
> >> Ha ha!  I don't know if you're back from shopping yet...and I'm not
> sure that I've broken it (cobalt branch)...but it has broken my router!
> >
> > Hmm.  It’s been running all day with plenty of traffic over here - but
> it did crash the very first time I loaded it, just not the second.  I will
> need to exercise it some more, preferably on a non-critical machine.
>
> Okay, that bug is fixed and I’ve made further improvements to the
> triple-isolate algorithm.  It no longer needs quite as much spaghetti logic
> in the fast path, and might even be easier to understand from reading the
> code, since it’s now more obviously a modification of DRR++ rather than a
> brute-force wrapper around it.  It should certainly give smoother behaviour
> and be less CPU intensive in common cases.
>
> In brief, what I now do is to scale the *flow* quantum down by the higher
> of the two hosts’ flow counts.  I’ve even dealt with underflow of the
> quotient using a dithering mechanism, which should also ensure that flows
> random-walk out of lockstep with each other.
>
> It works sufficiently well that I was able to set Cake to 2.5Mbit
> besteffort triple-isolate, then watch a 720p YouTube video on one machine
> while another was downloading a game update using a 30-flow swarm.  I’d
> call that a success.
>
> Hammer away at it, and then we’ll see if we can merge it up to master.
>
>  - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net <javascript:;>
> https://lists.bufferbloat.net/listinfo/cake
>

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

      reply	other threads:[~2016-10-11 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04  7:22 Jonathan Morton
2016-10-04  8:46 ` moeller0
2016-10-04 11:18   ` Jonathan Morton
2016-10-04 11:54     ` moeller0
2016-10-04 16:23       ` Loganaden Velvindron
2016-10-04 15:22 ` Kevin Darbyshire-Bryant
2016-10-04 16:28   ` Jonathan Morton
2016-10-11  5:41     ` Jonathan Morton
2016-10-11 12:09       ` Luis E. Garcia [this message]

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=CALnBQ5nAW6f8eWBxzAMecKPqeyFU9vLYL_qbbE7JJSEGv2Rq3g@mail.gmail.com \
    --to=luis@bitamins.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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