CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	codel@lists.bufferbloat.net,
	 bloat-announce@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net
Subject: [Codel] DOCSIS + Codel paper published by cablelabs
Date: Mon, 26 Nov 2012 22:11:24 +0100	[thread overview]
Message-ID: <CAA93jw5J2MZ4ZmkP4UekPaYqmXBGkyyp3CA9xfGN9o-ds5PmMA@mail.gmail.com> (raw)

Recently Greg White and a few others at Cablelabs, along with Kathie
Nichols, did an exhaustive simulation of a cable modem with a default
amount of buffering, vs the new short queue option, vs codel, in a
wide variety of scenarios.

The paper has just been released officially.

http://www.cablelabs.com/downloads/pubs/PreliminaryStudyOfCoDelAQMinaDOCSISNetwork.pdf

If you dig deeply into it, you'll see how really small queues can hurt
performance (so don't do that), the effect of losing TCP syns in drop
tail (don't saturate your buffers!), the effects of overbuffering at
the driver level (hard to tell what reducing that will do in this
sim), and a few other things like that.

One problem with the web portion of the sim is that it doesn't
simulate enough streams, and more importantly, it doesn't emulate the
effects of DNS lookups. Still, it's interesting and more accurate than
many others tests.

I'm relatively happy with the voip test therein, although I structured
the rrul equivalent to be much more difficult than the simulated one.

And if you look at the (fairly few) places in the paper where codel
doesn't shine, and think about where fq_codel compensates for that,
you might go to bed with a glow on.

I look forward to the followup paper.

Thx cablelabs and kathie!

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

                 reply	other threads:[~2012-11-26 21:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw5J2MZ4ZmkP4UekPaYqmXBGkyyp3CA9xfGN9o-ds5PmMA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@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