From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] 900mbit tbf + fq_codel vs cake on the apu2
Date: Wed, 22 Aug 2018 09:11:56 -0700 [thread overview]
Message-ID: <CAA93jw5QPne4qFdJcyc1WWjuZi=X4d+zpWJ1Q63i7jbgqoAPYw@mail.gmail.com> (raw)
In-Reply-To: <69F43477-6578-4237-AB03-E90357142C89@heistp.net>
On Wed, Aug 22, 2018 at 9:08 AM Pete Heist <pete@heistp.net> wrote:
>
>
> > On Aug 22, 2018, at 5:10 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > adding a basic shaper to fq_codel itself is kind of trivial. You need
> > to check if you are shaping
> >
> > this was 40% faster than tbf + fq_codel in the good ole days and I
>
> Aha, ok, I didn't there was that much to be gained in serial performance.
>
> > versions of cake... dunno. I *personally* need an inbound shaper that
> > cracks 120mbit on mips hardware.
>
> The FreeNet guys upgraded our sector to AC last week, so I switched to a PowerBeam AC (wrecked my legs straddling the peak of a 45 degree roof for half a day). Anyway, I would also like if my ER-X (32-bit mips) had some more headroom to run something codel-like. It can do it, but it starts to struggle. Mine is currently an htb+cake setup.
well, how much cpu can you claw back with tbf + fq_codel?
note that tbf IS sensitive to the burst size. 64k might be too much.
Or too little.
> > ...
> > I hadn't thought about additionally parallelizing the workload (which
> > has problems like adding way more queues than I'd like) much.
>
> I thought there was already some discussion about that wrt lockless qdisc support, which doesn’t mean adding more queues, or multiple qdisc instances, does it? Perhaps my understanding of what that does and use of the term “smp” was loose...
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
prev parent reply other threads:[~2018-08-22 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 21:31 Dave Taht
2018-08-22 8:51 ` Pete Heist
2018-08-22 14:23 ` Dave Taht
2018-08-22 15:10 ` Dave Taht
2018-08-22 16:08 ` Pete Heist
2018-08-22 16:11 ` Dave Taht [this message]
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='CAA93jw5QPne4qFdJcyc1WWjuZi=X4d+zpWJ1Q63i7jbgqoAPYw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=pete@heistp.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