CoDel AQM discussions
 help / color / mirror / Atom feed
From: Kathleen Nichols <nichols@pollere.com>
To: codel@lists.bufferbloat.net
Subject: Re: [Codel] what RTT was fig 7 in the codel paper?
Date: Tue, 1 Dec 2015 17:17:26 -0800	[thread overview]
Message-ID: <565E46A6.4060207@pollere.com> (raw)
In-Reply-To: <CAA93jw69ao9kmkCN97kg2_JCY7rSJyeooaJR449CwXKo2O14kg@mail.gmail.com>


Oh, that would have been 100 ms unloaded.

On 12/1/15 10:08 AM, Dave Taht wrote:
> What RTT was fig 7 in the codel paper? (the one that showed codel's
> reaction to bandwidth changes?)
> http://queue.acm.org/detail.cfm?id=2209336
> 
> I am amusing myself by trying to create an automated string of flent
> tests to duplicate those results, now that flent has gained tools that
> can plot queue depth as well as ping, we have a testbed with fully
> controllable RTT, etc.
> 
> http://snapon.cs.kau.se/~d/nichols/basiccodel.png
> 
> "To roughly emulate a (nominal) 100-Mbps Wi-Fi link subject to
> degradation, we used a load of four FTPs and five Web connections per
> second and changed link rates at 50-second intervals (over the 300
> simulated seconds), first dropping to 10 Mbps, then to 1 Mbps, then
> jumping to 50 Mbps, dropping to 1 Mbps, and finally jumping back to
> 100 Mbps. Buffer capacity is a single BDP (830 packets) for the
> nominal rate. This scenario was repeated for CoDel, Tail Drop, and
> RED. "
> 
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> https://www.gofundme.com/savewifi
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
> 


      reply	other threads:[~2015-12-02  1:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 18:08 Dave Taht
2015-12-02  1:17 ` Kathleen Nichols [this message]

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=565E46A6.4060207@pollere.com \
    --to=nichols@pollere.com \
    --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