From: John Yates <john@yates-sheets.org>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Pete Heist <pete@eventide.io>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Pre-print of Cake paper available
Date: Tue, 24 Apr 2018 11:08:25 -0400 [thread overview]
Message-ID: <CAJnXXogj3_Ho=re2M6v5nbzNUtWLrwhtM+dtt16iAzEJ+7tD3Q@mail.gmail.com> (raw)
In-Reply-To: <0E96CBE1-B3B8-4E2A-BB09-1EEDD4E390BF@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On Tue, Apr 24, 2018 at 4:17 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> That is true to some degree, but the overall algorithm is not that hard:
Set the shaper at 50% of contracted rate and measure the bufferbloat
(depending on the expertise of the user either via flent or the dslreports
speedtest); if bufferbloat acceptable set shaper higher (by 50% of the
remaining difference to 100% contracted rate) or if unaceptable lower.
Really just a binary search for the acceptable limits. Now this should be
done individually for each shaper direction. The final proof of the pudding
is to see how this shaper copes with a bi-directional saturating load (like
flent's rrul).
Given that the target audience is VCR-owning home users could this be
reduced to a scripts? Then perhaps hardware vendors could then expose it
in their GUI.
/john
[-- Attachment #2: Type: text/html, Size: 1345 bytes --]
next prev parent reply other threads:[~2018-04-24 15:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 8:39 Toke Høiland-Jørgensen
2018-04-23 9:54 ` Jonathan Morton
2018-04-23 23:01 ` Pete Heist
2018-04-23 23:31 ` Jonathan Morton
2018-04-24 5:44 ` Pete Heist
2018-04-24 5:58 ` Jonathan Morton
2018-04-24 7:15 ` Pete Heist
2018-04-24 7:56 ` Sebastian Moeller
2018-04-24 8:45 ` Toke Høiland-Jørgensen
2018-04-24 8:57 ` Pete Heist
2018-04-25 18:44 ` David Lang
2018-04-25 20:28 ` Toke Høiland-Jørgensen
2018-04-26 19:27 ` Pete Heist
2018-04-27 11:08 ` Toke Høiland-Jørgensen
2018-04-27 11:20 ` Pete Heist
2018-04-24 8:17 ` Sebastian Moeller
2018-04-24 8:47 ` Toke Høiland-Jørgensen
2018-04-24 8:50 ` Jonathan Morton
2018-04-24 9:06 ` Pete Heist
2018-04-24 9:15 ` Toke Høiland-Jørgensen
2018-04-24 9:36 ` Pete Heist
2018-04-24 9:18 ` Sebastian Moeller
2018-04-24 9:30 ` Toke Høiland-Jørgensen
2018-04-24 9:38 ` Sebastian Moeller
2018-04-24 9:44 ` Toke Høiland-Jørgensen
2018-04-24 15:08 ` John Yates [this message]
2018-04-24 8:43 ` Toke Høiland-Jørgensen
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='CAJnXXogj3_Ho=re2M6v5nbzNUtWLrwhtM+dtt16iAzEJ+7tD3Q@mail.gmail.com' \
--to=john@yates-sheets.org \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=pete@eventide.io \
/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