CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Tobias Diedrich <ranma+openwrt@tdiedrich.de>,
	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: Tue, 22 May 2012 02:29:52 +0100	[thread overview]
Message-ID: <CAA93jw46Dos+fDATXkB+6KPMxp+47AnF2gxJg0gdyXGYQC-RGg@mail.gmail.com> (raw)
In-Reply-To: <4FBAEA65.2090601@hp.com>

I would really like people to clearly mark when they are using pfifo_fast,
codel, and fq_codel.

Secondly, I note that for utterly best results it is useful to ALSO have
htb on on ingress to a value only slightly lower than the rate under
test, and fq_codel attached to
the bin(s)

(an example of this is in the deBloat repo on github - both ingress.sh
and simple_qos.sh)

It would be nice if doing ingress was as simple as egress, maybe using some sort
of tbf + fq_codel....

Otherwise for some benchmarks... at 100Mbit, you will see TCP_STREAM
behavior holding
the line at ~5ms, and TCP_MAERTS being in excess of 30ms, especially
when pfifo_fast is on the other
side. Or vice versa, depending on where you are running the test.

On Tue, May 22, 2012 at 2:22 AM, Rick Jones <rick.jones2@hp.com> wrote:
> 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
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

  reply	other threads:[~2012-05-22  1:29 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
2012-05-22  1:29                   ` Dave Taht [this message]
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=CAA93jw46Dos+fDATXkB+6KPMxp+47AnF2gxJg0gdyXGYQC-RGg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=ranma+openwrt@tdiedrich.de \
    --cc=rick.jones2@hp.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