From: Georgios Amanakis <gamanakis@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [Fwd: Re: RHODIUM - nuking blue (for testing)]
Date: Wed, 6 Dec 2017 16:43:02 -0500 [thread overview]
Message-ID: <CACvFP_iCWP+bfOQkp46KLV9Txv90Abcsf3yWSpP5xasGvzZR_w@mail.gmail.com> (raw)
In-Reply-To: <CACvFP_g-Av1sJJakE_fMJQ-A1Vgi2qk2xiJc1yOaoy-sWb084g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]
Redid the triple-isolate/{no-ack-filter, ack-filter-aggressive} with
Cobalt/Rhodium.
ping_cdf, tcp_rtt_cdf and cpu plots.
No apparent difference in CPU usage.
On Wed, Dec 6, 2017 at 4:21 PM, Georgios Amanakis <gamanakis@gmail.com>
wrote:
> I will rerun this one, just to be sure.
>
> On Wed, Dec 6, 2017 at 4:17 PM, Georgios Amanakis <gamanakis@gmail.com>
> wrote:
>
>>
>> On Wed, Dec 6, 2017 at 4:08 PM, Dave Taht <dave@taht.net> wrote:
>>
>>>
>>> Did you get cpu stats for the below tests?
>>>
>>> I did! In the no-ack-filter case CPU usage looks strange though. Seems
>> to be higher with Rhodium.
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1570 bytes --]
[-- Attachment #2: cpu_cake_cakerhod.png --]
[-- Type: image/png, Size: 632755 bytes --]
[-- Attachment #3: ping_cdf_cake_cakerhod_ackaggr.png --]
[-- Type: image/png, Size: 386226 bytes --]
[-- Attachment #4: ping_cdf_cake_cakerhod_noack.png --]
[-- Type: image/png, Size: 342039 bytes --]
[-- Attachment #5: rtt_cdf_cake_cakerhod_ackaggr.png --]
[-- Type: image/png, Size: 810020 bytes --]
[-- Attachment #6: rtt_cdf_cake_cakerhod_noack.png --]
[-- Type: image/png, Size: 683106 bytes --]
[-- Attachment #7: rrulbe_cmts_rhodium_cobalt.tgz --]
[-- Type: application/x-gzip, Size: 4139772 bytes --]
next prev parent reply other threads:[~2017-12-06 21:43 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
[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 [this message]
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=CACvFP_iCWP+bfOQkp46KLV9Txv90Abcsf3yWSpP5xasGvzZR_w@mail.gmail.com \
--to=gamanakis@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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