From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake not more CPU efficient than HTB+FQ-CoDel (anymore)?
Date: Wed, 11 Apr 2018 20:59:59 +0300 [thread overview]
Message-ID: <50C2E3D7-975E-4067-9F0C-E32FD6C26041@gmail.com> (raw)
In-Reply-To: <87vacx8wj7.fsf@toke.dk>
> On 11 Apr, 2018, at 8:47 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>>> Also would be nice to get a measure of the smoothness of the
>>> shaper; will see if I can't extract that from a pcap file or
>>> something
>>
>> I remember using tcptrace for that purpose, once upon a time.
>
> Yup, that was my plan as well. Just not sure whether it has a metric
> that is better than "look, the graph is smoother"... ;)
It does have a throughput graph available. However, this is based on raw inter-packet spacing, so it'll have line-rate bursts interspersed by very short gaps if Cake experiences any scheduling latency greater than the serialisation delay of one MTU.
The best counter to that might be to select a low rate, so that the serialisation delay is 1-2ms or so. It should then be easy to contrast with HTB's behaviour at that same rate.
- Jonathan Morton
next prev parent reply other threads:[~2018-04-11 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 15:24 Toke Høiland-Jørgensen
2018-04-11 15:41 ` Jonathan Morton
2018-04-11 17:15 ` Toke Høiland-Jørgensen
2018-04-11 17:23 ` Jonathan Morton
2018-04-11 17:47 ` Toke Høiland-Jørgensen
2018-04-11 17:59 ` Jonathan Morton [this message]
2018-04-11 18:55 ` Jonas Mårtensson
2018-04-11 19:08 ` Toke Høiland-Jørgensen
2018-04-11 19:26 ` Sebastian Moeller
2018-04-11 19:30 ` Sebastian Moeller
2018-04-11 19:56 ` Jonas Mårtensson
2018-04-12 10:48 ` Toke Høiland-Jørgensen
2018-04-11 16:03 ` Pete Heist
2018-04-11 17:16 ` Toke Høiland-Jørgensen
2018-04-14 4:48 ` There is cake qdisc manual Y
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=50C2E3D7-975E-4067-9F0C-E32FD6C26041@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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