From: Jonathan Morton <chromatix99@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: bloat Mainlinglist <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Comcast upped service levels -> WNDR3800 can't cope...
Date: Sat, 30 Aug 2014 23:47:57 +0300 [thread overview]
Message-ID: <4DA71387-6720-4A2F-B462-2E1295604C21@gmail.com> (raw)
In-Reply-To: <4FF4917C-1B6D-4D5F-81B6-5FC177F12BFC@gmail.com>
On 30 Aug, 2014, at 8:33 pm, Jonathan Morton wrote:
> I'll need to investigate more closely to see whether there's a CPU load difference between HTB and TBF in practice.
Replying to myself, but...
The surprising result is that TBF seems to consume about TWICE the CPU time, at the same bandwidth, as HTB does. Even FQ in flow-rate-limit mode is roughly on par with HTB on that score. There is clearly something very wrong with how TBF is doing it.
HTB (running with only a default class) and FQ are both able to send and regulate 200Mbps using about an eighth of a 1.5GHz PowerPC, all told. It doesn't even seem to matter which qdisc I slap on top of HTB. TBF needs almost a quarter of the same CPU to do the same thing.
- Jonathan Morton
next prev parent reply other threads:[~2014-08-30 20:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 16:57 [Cerowrt-devel] " Aaron Wood
2014-08-29 17:03 ` [Cerowrt-devel] [Bloat] " Rick Jones
2014-08-29 17:15 ` Jonathan Morton
2014-08-29 17:19 ` Jonathan Morton
2014-08-29 17:25 ` Sebastian Moeller
2014-08-29 18:06 ` Dave Taht
2014-08-30 11:02 ` Jonathan Morton
2014-08-30 13:03 ` Toke Høiland-Jørgensen
2014-08-30 17:33 ` Jonathan Morton
2014-08-30 20:47 ` Jonathan Morton [this message]
2014-08-30 22:30 ` Dave Taht
2014-08-31 10:18 ` Jonathan Morton
2014-08-31 10:21 ` Toke Høiland-Jørgensen
2014-09-01 17:01 ` Dave Taht
2014-09-01 18:06 ` Jonathan Morton
2014-09-01 18:32 ` Dave Taht
2014-09-01 20:25 ` Aaron Wood
2014-09-01 21:43 ` Jonathan Morton
2014-09-01 22:14 ` Aaron Wood
2014-09-02 9:09 ` David Lang
2014-09-02 9:27 ` Jonathan Morton
2014-09-02 10:05 ` Joel Wirāmu Pauling
2014-09-02 10:05 ` Joel Wirāmu Pauling
2014-09-03 6:15 ` Aaron Wood
2014-09-03 6:36 ` David Lang
2014-09-03 11:08 ` Jonathan Morton
2014-09-03 15:12 ` Aaron Wood
2014-09-03 19:22 ` Sebastian Moeller
2014-09-03 19:30 ` Dave Taht
2014-09-03 23:17 ` Bill Ver Steeg (versteb)
2014-09-04 0:33 ` Dave Taht
2014-09-04 3:36 ` Jonathan Morton
2014-09-04 14:05 ` Bill Ver Steeg (versteb)
2014-09-04 15:10 ` Michael Richardson
2014-09-04 7:04 ` Sebastian Moeller
2014-09-04 11:15 ` Jonathan Morton
2014-09-04 11:23 ` Sebastian Moeller
2014-09-02 8:55 ` Sebastian Moeller
2014-09-02 13:40 ` Jonathan Morton
2014-09-02 13:49 ` Sujith Manoharan
2014-09-02 15:37 ` Dave Taht
2014-09-02 15:47 ` Jonathan Morton
2014-09-02 15:57 ` Sujith Manoharan
2014-09-02 17:36 ` Jonathan Morton
2014-09-02 17:41 ` Dave Taht
2014-09-02 18:28 ` Jonathan Morton
2014-09-03 11:04 ` Jonathan Morton
2014-08-30 21:53 ` Stephen Hemminger
2014-08-30 11:14 ` Jonathan Morton
2014-08-30 17:19 ` Aaron Wood
2014-08-30 18:01 ` Jonathan Morton
2014-08-30 18:21 ` Sebastian Moeller
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA71387-6720-4A2F-B462-2E1295604C21@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.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