Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] qos calculator & paper for htb rate selection
Date: Sun, 19 Jun 2016 06:43:01 +0300	[thread overview]
Message-ID: <480A221C-E51E-4A77-A0DA-105DD2E0E427@gmail.com> (raw)
In-Reply-To: <CAA93jw5gcBbvib2eHu-+=vpgChm-NPcoRMJ=Pp_nqNDwq2yoSQ@mail.gmail.com>


> On 19 Jun, 2016, at 03:53, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I was attracted to reading it because
> it attempted to take our "85%" rule for sqm-scripts on downloads and
> attach some science to it...

At no point in that paper did I see any realisation that the initial burst permitted by a token bucket shaper would typically collect in a downstream dumb queue.  I can forgive them not knowing about deficit-mode shapers which have no initial burst, but they do not even try to adjust the burst size of the token bucket shaper.

Perhaps they considered that with the link fully loaded during each test, and with the physical link capacity unrestricted, the size of the burst was unimportant - but this still meant that a quantity of traffic at the beginning of each test was transmitted at line rate, not at the shaped rate.  This is an inherent hazard with using a token bucket shaper as a bandwidth reference.

They also seemed to devote a lot of space and effort to determining the correct queue size for a dump FIFO “behind” the shaper - something which AQM would handle for them.  When they did add AQM, they measured the delays to individual bulk flows rather than the delays to sparse flows competing with the bulk traffic, and thus obtained results showing AQM giving much larger delays to traffic than an “optimally sized” dumb FIFO.

As for the optimal sizing, it was performed on a LAN without any delay lines introduced to simulate realistic Internet RTTs.  They therefore obtained optimal sizes that were very small, and ended up comparing them against AQMs configured for Internet-scale RTTs, while still in the low-latency LAN environment.  This also gave AQM an unfair handicap.

With all these shortcomings, I can’t trust that any of the results they obtained would have any relevance to a realistic Internet application.

 - Jonathan Morton


  reply	other threads:[~2016-06-19  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-19  0:53 Dave Taht
2016-06-19  3:43 ` Jonathan Morton [this message]
2016-06-19  4:20   ` Dave Taht
2016-06-19 18:37 ` moeller0

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=480A221C-E51E-4A77-A0DA-105DD2E0E427@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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