From: Sebastian Moeller <moeller0@gmx.de>
To: Pete Heist <peteheist@gmail.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] small cake_hash optimization?
Date: Thu, 23 Nov 2017 09:00:31 +0100 [thread overview]
Message-ID: <BA486EAF-4DD2-4E6F-9927-61A36E2AF7FD@gmx.de> (raw)
In-Reply-To: <E3880313-03A9-4C9B-B170-9DA9F1FE8E52@gmail.com>
Hi Pete,
> On Nov 22, 2017, at 19:43, Pete Heist <peteheist@gmail.com> wrote:
>
>
>> On Nov 22, 2017, at 7:33 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> On Wed, Nov 22, 2017 at 4:37 AM, Pete Heist <peteheist@gmail.com> wrote:
>>>
>>> Ok, at least a little crude testing with sar:
>>>
>>> https://docs.google.com/spreadsheets/d/1LKoq5NaswuHm9H1atXoZA1AhNDg6L4UYS3Pn5lCsb1I/edit#gid=0
>>>
>>> ~10% less cake CPU at GigE in this case?
>>
>> Divides do hurt, particularly if you can't do them out of order. But
>> that seems like a lot.
>
> Hrm, I tried a second test to make sure fairness still works (it does) but this time got a slight _negative_ result (rrul_be fair tab). So this calls into question whether or not my testing method is very good, and also whether or not the change actually helps much.
>
> This time I used "cake unlimited besteffort dual-srchost overhead 64 mpu 84” (overheads from Sebastian, just rely on bql).
I should have mentioned "overhead 64 mpu 84" only make sense in combination with a shaper limit (well, they will make sure the cake statistics will be more reflective of what is happening on the ethernet wire, but I am not sure whether that is worth the run-time cost the overhead calculation incurs).
Somewhat unrelated, I wondered about all the excitement about irtt and cloned the repository to my mac, and was absolutely delighted to realize that irtt will also effortlessly work under macos. I only have run the demo from the readme.md with both client and server running at the same machine, but I got results that look reasonable on first sight (but I admit I really do not know exact;y what to expect). This is really great!
Best Regards
>
> I might try again with 950mbit limiting, and ‘perf’ instead.
>
> Also I noted that the ‘lan’ keyword seemed to adversely affect host fairness, so I stopped using it. I’ll address that separately when there’s time.
>
>>> What’s a better tool for timing
>>> kernel module functions?
>>
>> Use "perf"
>>
>> https://en.wikipedia.org/wiki/Perf_(Linux)
>
> Ok, will see if I can give it a try.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-11-23 8:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 10:06 Pete Heist
2017-11-22 12:37 ` Pete Heist
2017-11-22 13:51 ` Sebastian Moeller
2017-11-22 18:33 ` Dave Taht
2017-11-22 18:43 ` Pete Heist
2017-11-23 8:00 ` Sebastian Moeller [this message]
2017-11-23 9:30 ` Pete Heist
2017-11-23 9:36 ` Pete Heist
2017-11-23 16:21 ` Dave Taht
2017-11-23 16:48 ` Sebastian Moeller
2017-11-23 16:57 ` Dave Taht
2017-11-23 10:22 ` Sebastian Moeller
2017-11-22 18:38 ` Dave Taht
2017-11-22 18:49 ` Pete Heist
2017-11-22 21:19 ` Pete Heist
2017-11-22 21:26 ` Dave Taht
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=BA486EAF-4DD2-4E6F-9927-61A36E2AF7FD@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=peteheist@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