From: Jonathan Morton <chromatix99@gmail.com>
To: Simon Barber <simon@superduper.net>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Tue, 28 Jul 2015 17:43:25 +0300 [thread overview]
Message-ID: <628EB9BF-C35C-4CC1-A8D5-EE66486232E0@gmail.com> (raw)
In-Reply-To: <14ed5136170.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net>
> On 28 Jul, 2015, at 17:31, Simon Barber <simon@superduper.net> wrote:
>
> The issue is that Codel tries to keep the delay low, and will start dropping when sojourn time grows above 5ms for 100ms. For longer RTT links more delay is necessary to avoid underutilizing the link.
I’m pretty sure we’ve had this discussion before, several times.
Codel works pretty well, with an interval of 100ms, when the actual RTT is between about 10ms and 1000ms. That accounts for 99.9% of the practical paths you’ll see on the Internet.
If you really are concerned about long-RTT paths, then you can increase the interval parameter to suit. This will hurt Codel’s performance slightly on very short-RTT paths.
- Jonathan Morton
next prev parent reply other threads:[~2015-07-28 14:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:09 Juliusz Chroboczek
2015-07-28 13:33 ` Toke Høiland-Jørgensen
2015-07-28 13:50 ` Juliusz Chroboczek
2015-07-28 14:05 ` Toke Høiland-Jørgensen
2015-07-28 14:11 ` Simon Barber
2015-07-28 14:21 ` Eric Dumazet
2015-07-28 14:31 ` Simon Barber
2015-07-28 14:43 ` Jonathan Morton [this message]
2015-07-28 14:49 ` Eric Dumazet
2015-07-28 14:55 ` Eric Dumazet
2015-07-28 16:02 ` Alan Jenkins
2015-07-28 16:22 ` Sebastian Moeller
2015-07-28 17:11 ` Michael Welzl
2015-07-29 7:19 ` David Lang
2015-07-28 19:20 ` Juliusz Chroboczek
2015-07-28 19:29 ` Alan Jenkins
2015-07-28 14:18 ` Eric Dumazet
2015-07-28 14:44 ` Dave Taht
2015-07-28 14:52 ` Eric Dumazet
2015-07-28 19:24 ` Juliusz Chroboczek
2015-07-28 19:31 ` Bill Ver Steeg (versteb)
2015-07-28 20:10 ` Alan Jenkins
2015-07-28 20:45 ` Alan Jenkins
2015-07-29 13:15 ` Stefan Alfredsson
2015-07-29 13:41 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=628EB9BF-C35C-4CC1-A8D5-EE66486232E0@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=simon@superduper.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