From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
cake@lists.bufferbloat.net,
"marco maniezzo" <marco.maniezzo@gmail.com>
Subject: Re: [Cake] [CAKE] Rate is much lower than expected - CPU load is higher than expected
Date: Tue, 23 Jun 2020 19:25:57 +0300 [thread overview]
Message-ID: <5EB6FFEF-7206-40BE-BCDB-74E99DD316E1@gmail.com> (raw)
In-Reply-To: <0D78908A-07BB-4398-BFD2-78858AB2B8E2@gmx.de>
> On 23 Jun, 2020, at 7:08 pm, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> But I assume that you bound the bursts somehow, do you remember your bust sizing method by chance?
It bursts exactly enough to catch up to the schedule. No more, no less - unless the queue is emptied in the process.
- Jonathan Morton
prev parent reply other threads:[~2020-06-23 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 13:10 Jose Blanquicet
2020-06-22 14:25 ` Y
2020-06-22 15:47 ` Toke Høiland-Jørgensen
2020-06-23 13:05 ` Jose Blanquicet
2020-06-23 14:41 ` Toke Høiland-Jørgensen
2020-06-23 15:21 ` Jonathan Morton
2020-06-23 16:08 ` Sebastian Moeller
2020-06-23 16:25 ` Jonathan Morton [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=5EB6FFEF-7206-40BE-BCDB-74E99DD316E1@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=marco.maniezzo@gmail.com \
--cc=moeller0@gmx.de \
--cc=toke@redhat.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