From: Georgios Amanakis <gamanakis@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] [Fwd: Re: RHODIUM - nuking blue (for testing)]
Date: Tue, 05 Dec 2017 21:01:22 -0500 [thread overview]
Message-ID: <1512525682.21401.13.camel@gmail.com> (raw)
In-Reply-To: <1512525519.21401.11.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
-------- Forwarded Message --------
From: Georgios Amanakis <gamanakis@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>, Jonathan Morton <chromatix9
9@gmail.com>, Pete Heist <peteheist@gmail.com>
Subject: Re: [Cake] RHODIUM - nuking blue (for testing)
Date: Tue, 05 Dec 2017 20:58:39 -0500
I just finished testing Rhodium, and I am supplementing Sunday's
results.
CMTS setup:
server -- delay -- isp -- mbox -- client
ISP limited at 200/10mbit.
Cake/HTB shaping at 180/9mbit.
RTT 20ms with cake's RTT set at 20ms
rrul_be_nflows, 32 download, 8 upload streams.
net.ipv4.tcp_ecn=2 in all nodes (linux default)
Cake tested in all flow-isolation modes with all ack filtering options.
HTB tested with codel,pie,fq,sfq,fq_codel.
Rhodium(cakerhod) doesn't show much difference against Cobalt(cake).
George
On Tue, 2017-12-05 at 11:32 -0800, Dave Taht wrote:
> Given some of the results thus far at various RTTs, and at higher
> loads, like the ginormous one georgios just ran, I thought it might
> be
> useful to run a battery of tests with blue disabled.
>
> I haven't gone to the trouble of creating a formal branch - tho if I
> did, I'd call it rhodium, as rhodium detectors are used in nuclear
> reactors to measure the neutron flux level.
>
> untested-but-compiling-patch attached. I'm busy on a few other things
> this week, and it is looking like we'll have to replace the xstats
> structure with something smaller to go mainline.
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
[-- Attachment #2: ping_cdf_cobalt_rhodium_noack.png --]
[-- Type: image/png, Size: 110103 bytes --]
[-- Attachment #3: tcp_rtt_cobalt_rhodium_noack.png --]
[-- Type: image/png, Size: 180626 bytes --]
[-- Attachment #4: ping_cdf_cobalt_rhodium_ackaggr.png --]
[-- Type: image/png, Size: 114693 bytes --]
[-- Attachment #5: tcp_rtt_cobalt_rhodium_ackaggr.png --]
[-- Type: image/png, Size: 183707 bytes --]
next parent reply other threads:[~2017-12-06 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512525519.21401.11.camel@gmail.com>
2017-12-06 2:01 ` Georgios Amanakis [this message]
[not found] ` <CAJq5cE3rqrHSCgdU9rw3dXrW8A7sNTuFtxEXddPHh9Rmqzh3qg@mail.gmail.com>
[not found] ` <CAJq5cE2rm0jbEyCMWrYcXqkqL=aXtd2jhkRzowvRx_usLo+-sQ@mail.gmail.com>
2017-12-06 2:09 ` Jonathan Morton
2017-12-06 21:08 ` Dave Taht
2017-12-06 21:17 ` Georgios Amanakis
2017-12-06 21:21 ` Georgios Amanakis
2017-12-06 21:43 ` Georgios Amanakis
2017-12-06 22:35 ` Luis E. Garcia
2017-12-07 1:15 ` Dave Taht
2017-12-07 8:40 ` Pete Heist
2017-12-07 2:19 ` Jonathan Morton
2017-12-07 9:08 ` Kevin Darbyshire-Bryant
2017-12-07 9:16 ` 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=1512525682.21401.13.camel@gmail.com \
--to=gamanakis@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