CoDel AQM discussions
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	codel@lists.bufferbloat.net
Subject: Re: [Codel] BQL support in Ethernet drivers (and Kathie Nichols and Van Jacobson's new AQM, codel)
Date: Mon, 21 May 2012 18:22:45 -0700	[thread overview]
Message-ID: <4FBAEA65.2090601@hp.com> (raw)
In-Reply-To: <4FBAD015.4040907@hp.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

On 05/21/2012 04:30 PM, Rick Jones wrote:
> I think my original ones had the unfortunate effect of putting lines on
> top of one another. Your's seem to put them pretty far apart (at least
> sometimes). We aught to be able to find some reasonable medium in there
> somewhere. I'm thinking if latency is the metric of greatest interest,
> we want that to have the full y axis, and then the peak bandwidth of the
> STREAM test be about half-way up?

I've tweaked the bloat.sh script in a couple ways.  First, I changed how 
I compute the scaling factor, to implement what I described above. 
Second, I am using a negative value for the demo interval for the TCP_RR 
test.  This causes netperf to check if it is time to emit a result after 
each transaction rather than after what it thought would be the number 
of transactions in the interval.  In that way the latency line is much 
more robust in the face of a sudden bloating of the path.  The effect on 
transactions per second should be similar to that of enabling 
histograms.  An example of a test across my 100 Mbit/s link to a laptop 
is attached.

happy benchmarking,

rick jones

[-- Attachment #2: bloat.png --]
[-- Type: image/png, Size: 33750 bytes --]

  reply	other threads:[~2012-05-22  1:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw6TcZGpxpS=DhuHCTWBn3uq1RbzugtJ3oJmA5zx9oDP-w@mail.gmail.com>
     [not found] ` <20120520212944.GK22418@yumi.tdiedrich.de>
     [not found]   ` <20120521003115.GO22418@yumi.tdiedrich.de>
2012-05-21  3:48     ` Dave Taht
2012-05-21 17:24       ` Rick Jones
2012-05-21 21:49         ` Tobias Diedrich
2012-05-21 22:17           ` Rick Jones
2012-05-21 22:20             ` Rick Jones
2012-05-21 23:09             ` Tobias Diedrich
2012-05-21 23:30               ` Rick Jones
2012-05-22  1:22                 ` Rick Jones [this message]
2012-05-22  1:29                   ` Dave Taht
2012-05-22  0:27           ` Dave Taht
2012-05-29 13:00             ` Tobias Diedrich

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=4FBAEA65.2090601@hp.com \
    --to=rick.jones2@hp.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=ranma+openwrt@tdiedrich.de \
    /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