From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Luca Muscariello <luca.muscariello@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] A few puzzling Cake results
Date: Thu, 19 Apr 2018 11:26:24 +0200 [thread overview]
Message-ID: <87y3hjzgvz.fsf@toke.dk> (raw)
In-Reply-To: <3B813EB8-92E7-402D-8BF5-DD43971155E4@gmail.com>
Jonathan Morton <chromatix99@gmail.com> writes:
>> your solution significantly hurts performance in the common case
>
> I'm sorry - did someone actually describe such a case? I must have
> missed it.
I started this whole thread by pointing out that this behaviour results
in the delay of the TCP flows scaling with the number of active flows;
and that for 32 active flows (on a 10Mbps link), this results in the
latency being three times higher than for FQ-CoDel on the same link.
This was the message:
https://lists.bufferbloat.net/pipermail/cake/2018-April/003405.html
And this graph, specifically:
https://lists.bufferbloat.net/pipermail/cake/attachments/20180417/1e56d8f3/attachment-0002.png
It's even worse for 64 flows, obviously; and there's no change in
goodput.
-Toke
next prev parent reply other threads:[~2018-04-19 9:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 9:42 Toke Høiland-Jørgensen
2018-04-17 10:04 ` Luca Muscariello
2018-04-17 10:38 ` Toke Høiland-Jørgensen
2018-04-17 12:05 ` Y
[not found] ` <mailman.225.1523966725.3573.cake@lists.bufferbloat.net>
2018-04-17 12:22 ` Toke Høiland-Jørgensen
2018-04-17 13:16 ` Jonas Mårtensson
2018-04-17 13:50 ` Toke Høiland-Jørgensen
2018-04-17 13:47 ` Luca Muscariello
2018-04-17 13:52 ` Luca Muscariello
2018-04-17 14:25 ` Toke Høiland-Jørgensen
2018-04-17 14:54 ` Luca Muscariello
2018-04-17 15:10 ` Toke Høiland-Jørgensen
2018-04-17 14:03 ` Jonathan Morton
2018-04-17 14:17 ` Toke Høiland-Jørgensen
2018-04-18 11:25 ` Toke Høiland-Jørgensen
2018-04-18 12:21 ` Kevin Darbyshire-Bryant
2018-04-18 12:57 ` Toke Høiland-Jørgensen
2018-04-18 13:13 ` Jonas Mårtensson
2018-04-18 13:21 ` Toke Høiland-Jørgensen
2018-04-18 14:12 ` Jonathan Morton
2018-04-18 14:30 ` Toke Høiland-Jørgensen
2018-04-18 15:03 ` Jonathan Morton
2018-04-18 15:17 ` Sebastian Moeller
2018-04-18 15:58 ` Jonathan Morton
2018-04-18 16:11 ` Toke Høiland-Jørgensen
2018-04-18 16:25 ` Dave Taht
2018-04-18 16:34 ` Georgios Amanakis
2018-04-18 17:10 ` Sebastian Moeller
2018-04-19 7:49 ` Luca Muscariello
2018-04-19 8:11 ` Jonathan Morton
2018-04-19 9:00 ` Toke Høiland-Jørgensen
2018-04-19 9:21 ` Jonathan Morton
2018-04-19 9:26 ` Toke Høiland-Jørgensen [this message]
2018-04-19 9:55 ` Jonathan Morton
2018-04-19 10:33 ` Toke Høiland-Jørgensen
2018-04-19 11:55 ` Luca Muscariello
2018-04-18 16:54 ` Jonathan Morton
2018-04-18 17:02 ` Dave Taht
2018-04-18 18:06 ` Jonas Mårtensson
2018-04-18 18:11 ` Toke Høiland-Jørgensen
2018-04-18 18:16 ` Kevin Darbyshire-Bryant
[not found] ` <mailman.238.1524075384.3573.cake@lists.bufferbloat.net>
2018-04-19 8:31 ` Kevin Darbyshire-Bryant
2018-04-18 18:11 ` Jonas Mårtensson
2018-04-18 19:53 ` David Lang
2018-04-18 21:53 ` Jonathan Morton
2018-04-19 9:22 ` Toke Høiland-Jørgensen
2018-04-19 9:32 ` 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=87y3hjzgvz.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=luca.muscariello@gmail.com \
/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