CoDel AQM discussions
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Wed, 01 May 2013 13:26:23 -0700	[thread overview]
Message-ID: <51817A6F.1080006@superduper.net> (raw)
In-Reply-To: <CAA93jw5y=n29wAf=rBdR9N0EZ+LX_OuA+XvPc705vcmun2bQzw@mail.gmail.com>

Interesting to note that sfq-codel's reaction to a non conforming flow 
is of course to start dropping more aggressively to make it conform, 
leading to the high loss rates for whatever is hashed together with a 
VoIP flow that does not reduce it's bandwidth.

One downside to SFQ really.

Simon

On Wed 01 May 2013 04:23:00 AM PDT, Dave Taht wrote:
> Greg White and his team over at cablelabs have just published their
> latest simulation results of the aqm algorithms under test on
> simulated cable modems.
>
> This paper is vastly expanded from the presentation at ietf 86 iccrg,
> including great descriptions the effects of latency on web, voice, and
> gaming traffic, and of codel, fq_codel, and pie. There's an excellent
> and deep section on the characteristics of gaming traffic, a ton of
> new graphs and analysis, and much much more.
>
> http://www.cablelabs.com/downloads/pubs/Active_Queue_Management_Algorithms_DOCSIS_3_0.pdf
>
> While I have a few quibbles, I'll reserve them until after more folk
> have had a chance to read this.
>
> It's good stuff.
>

  reply	other threads:[~2013-05-01 20:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:23 [Codel] " Dave Taht
2013-05-01 20:26 ` Simon Barber [this message]
2013-05-02  0:00   ` [Codel] [Bloat] " Jonathan Morton
2013-05-02  2:20     ` Simon Barber
2013-05-02  4:59       ` Andrew McGregor
2013-05-02 12:04       ` Jonathan Morton
2013-05-02 13:29         ` Simon Perreault
2013-05-14  2:26         ` Dan Siemon
2013-05-14  4:56           ` Tristan Seligmann
2013-05-14 10:24             ` Dave Taht
2013-05-14 13:02               ` Eric Dumazet
2013-06-11 18:19             ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-14 12:12           ` [Codel] " Jesper Dangaard Brouer
2013-05-06 17:54       ` Jesper Dangaard Brouer
2013-05-06 18:46         ` Jonathan Morton
2013-05-06 20:47           ` Jesper Dangaard Brouer
2013-05-07 16:22             ` Greg White
2013-05-07 13:31       ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` [Codel] [Bloat] [Cerowrt-devel] " Greg White
2013-05-07 19:56           ` [Codel] [Bloat] " Wes Felter
2013-05-07 20:30             ` Eric Dumazet
2013-05-08 22:25               ` Dave Taht
2013-05-08 22:54                 ` Eric Dumazet
2013-05-09  1:45                   ` Andrew McGregor

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=51817A6F.1080006@superduper.net \
    --to=simon@superduper.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@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