Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: George Amanakis <gamanakis@gmail.com>
To: "Jonathan Morton" <chromatix99@gmail.com>, "Dave Täht" <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake vs fqcodel with 1 client, 4 servers
Date: Wed, 06 Dec 2017 21:58:13 -0500	[thread overview]
Message-ID: <1512615493.10688.8.camel@gmail.com> (raw)
In-Reply-To: <CAJq5cE0TAsC57TW9i3nCT7KV806u7KtqFcU3FGfSuNuU9g4XYA@mail.gmail.com>

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

4servers  --   delay   --   isp   --   mbox   --   1client
netserver     10/10ms     10/2mbit    9/1.8mbit    flent

net.ipv4.tcp_ecn=2
11down/2upstream flows using 4 parallel rrul_be_nflows

cobalt branch
cake params: rtt 20ms triple-isolate ack-filter

cake_4mtu --> r402 with ingress
cake_noadjust --> r400 with ingress
cake_noing --> r400 without ingress



On Thu, 2017-12-07 at 04:27 +0200, Jonathan Morton wrote:
> The latest push now enforces 4 x MTU x flows on the target intra-flow 
> latency.  When lightly loaded, the normal target still applies.
> This gives a noticeable improvement on the goodput of World of
> Warships' updater, which does its level best to stuff 150 HTTP flows
> through my 512Kbps downlink, while retaining reasonable inter-flow
> latency as measured by using other applications and/or hosts.
> I'd like to see a more controlled test of this, to compare with the
> previous behaviour.
> - Jonathan Morton

[-- Attachment #2: rrulbe_11_4_4servers_1client_10mbit_2mbit_cake_ingress.tgz --]
[-- Type: application/x-compressed-tar, Size: 1927267 bytes --]

[-- Attachment #3: boxcombine_cake_ingress.png.png --]
[-- Type: image/png, Size: 104088 bytes --]

[-- Attachment #4: boxtotals_cake_ingress.png --]
[-- Type: image/png, Size: 133037 bytes --]

  parent reply	other threads:[~2017-12-07  2:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 22:30 Georgios Amanakis
2017-12-05  0:06 ` Dave Taht
2017-12-05  1:13   ` Georgios Amanakis
2017-12-05  1:38     ` Jonathan Morton
2017-12-05  3:50       ` George Amanakis
2017-12-05  4:48         ` Jonathan Morton
2017-12-05 21:15           ` Dave Taht
2017-12-05 21:26             ` Georgios Amanakis
2017-12-05 22:39               ` xnor
2017-12-06  9:37                 ` Jonathan Morton
2017-12-06 19:32                   ` xnor
     [not found]                     ` <CAJq5cE3MUfCuV_=GXAAOwvAXxee_dcJBaUkRVAEEWwyT5m7gAw@mail.gmail.com>
2017-12-07  1:59                       ` Jonathan Morton
2017-12-07  2:27             ` Jonathan Morton
2017-12-07  2:30               ` George Amanakis
2017-12-07  2:58               ` George Amanakis [this message]
2017-12-07  3:04                 ` Jonathan Morton
2017-12-07  3:08                   ` Georgios Amanakis
2017-12-07  7:08                     ` Jonathan Morton
2017-12-07  8:21                       ` Jonathan Morton
2017-12-07  8:51                         ` Kevin Darbyshire-Bryant
2017-12-07  9:03                           ` Jonathan Morton
2017-12-07 13:17                             ` Georgios Amanakis
2017-12-07 22:12                               ` xnor
2017-12-07 22:34                                 ` Georgios Amanakis

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=1512615493.10688.8.camel@gmail.com \
    --to=gamanakis@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave@taht.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