From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] apu2 sqm/htb issue + a minor win for speeding up fq_codel itself
Date: Tue, 4 Sep 2018 14:16:27 -0700 [thread overview]
Message-ID: <CAA93jw6m6PFjgqH6WLN4zkD9Ct_Q5sxnT4HK8d+SGasfOtt0=Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4e=1_ke22GGEOm2sHWKxa6ctnj5gt984GKWT7UoGNC+w@mail.gmail.com>
my guess is that burst and cburst should scale roughly as a function
of the bytes that can fit into 1ms.
On Tue, Sep 4, 2018 at 2:14 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> making htb's cburst and burst parameters 64k gets the APU2 up to
> where it can shape 900mbits. 3 ksoftirq handlers start getting cpu
> time, and we end up 54% idle to achiefe that.
>
> I should really go around running my own old code. I was deeply
> involved in sqm when we still had to run at sub 200mbit levels. since
> then it's been
> mostly tbf (burst 64k) + fq_codel or cake, and me ignoring various bug
> reports about it not scaling well enough at higher rates.
> On Tue, Sep 4, 2018 at 12:59 PM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > less than scientifically (via monitoring top) - on the apu2
> >
> > 100Mbit sqm (htb + fq_codel)
> >
> > fq_codel_mainline | fq_codel_fast
> > idle 78.8 | 83.5 |
> > si 20 | 16.1 |
> >
> > Yea! But:
> >
> > 900Mbit sqm (htb + fq_codel)
> >
> > fq_codel_mainline | fq_codel_fast
> > idle 74.4 | 74.4 |
> > si 25 | 25.1 |
> >
> > Here: completely bottlenecked on ksoftirqd - and I only get 340Mbits
> > out of the 900mbit setting. quantum 96k and burst of 15000. Haven't
> > fiddled with higher values yet...
> >
> >
> >
> > --
> >
> > Dave Täht
> > CEO, TekLibre, LLC
> > http://www.teklibre.com
> > Tel: 1-669-226-2619
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-09-04 21:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:59 Dave Taht
2018-09-04 21:14 ` Dave Taht
2018-09-04 21:16 ` Dave Taht [this message]
2018-09-06 17:51 ` [Cerowrt-devel] [Cake] " Pete Heist
2018-09-06 18:03 ` Dave Taht
2018-10-03 13:56 ` Mikael Abrahamsson
2018-10-03 14:44 ` Dave Taht
2018-10-03 14:45 ` Dave Taht
2018-10-03 15:30 ` Mikael Abrahamsson
2018-10-03 16:05 ` Dave Taht
2018-10-03 17:43 ` Toke Høiland-Jørgensen
2018-10-03 17:53 ` Dave Taht
2018-10-03 18:32 ` Jonathan Morton
2018-10-03 20:12 ` Toke Høiland-Jørgensen
2018-10-05 12:52 ` Mikael Abrahamsson
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='CAA93jw6m6PFjgqH6WLN4zkD9Ct_Q5sxnT4HK8d+SGasfOtt0=Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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