From: Jonathan Morton <chromatix99@gmail.com>
To: Pete Heist <peteheist@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake latency update
Date: Fri, 10 Feb 2017 10:49:36 +0200 [thread overview]
Message-ID: <B1561380-3DB9-4A11-AEA5-6775562A8971@gmail.com> (raw)
In-Reply-To: <830143EE-20F2-42A5-A4FC-ECE7DF50C632@gmail.com>
> On 10 Feb, 2017, at 10:04, Pete Heist <peteheist@gmail.com> wrote:
>
> I look forward to the throughput shifts being solved, where I see results like this:
>
> http://www.drhleny.cz/bufferbloat/cake_hd-eth-ap_100ms_80mbit/index.html
That basically looks like it’s run out of CPU, so there’s hard choices to make over CPU allocation. Cake isn’t responsible for that allocation, though it *might* be possible to optimise its use of the CPU a little further.
If you can obtain a CPU profile of that workload on that hardware, that might help to direct those efforts.
- Jonathan Morton
next prev parent reply other threads:[~2017-02-10 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:36 Pete Heist
2017-02-09 20:52 ` Jonathan Morton
2017-02-10 8:04 ` Pete Heist
2017-02-10 8:49 ` Jonathan Morton [this message]
2017-02-10 9:21 ` Pete Heist
2017-02-10 9:29 ` Jonathan Morton
2017-02-10 10:05 ` Pete Heist
2017-02-10 10:31 ` Jonathan Morton
2017-02-10 11:08 ` Pete Heist
2017-02-10 11:35 ` Sebastian Moeller
2017-02-10 12:21 ` Pete Heist
2017-02-12 12:43 ` Pete Heist
2017-02-12 13:08 ` Dave Taht
2017-02-12 14:12 ` Pete Heist
2017-02-12 16:37 ` Pete Heist
2017-02-12 16:41 ` Jonathan Morton
2017-02-12 17:15 ` Pete Heist
2017-02-14 10:02 ` Pete Heist
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=B1561380-3DB9-4A11-AEA5-6775562A8971@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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