Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] happy 4th!
Date: Mon, 08 Jul 2013 19:03:44 +0200	[thread overview]
Message-ID: <871u79x9kb.fsf@toke.dk> (raw)
In-Reply-To: <alpine.DEB.2.00.1307080211340.10894@uplift.swm.pp.se> (Mikael Abrahamsson's message of "Mon, 8 Jul 2013 02:24:25 +0200 (CEST)")

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

Mikael Abrahamsson <swmike@swm.pp.se> writes:

> I have not so far seen tests with FQ_CODEL with a simulated 100ms
> extra latency one-way (200ms RTT). They might be out there, but I have
> not seen them. I encourage these tests to be done.

Did a few test runs on my setup. Here are some figures (can't go higher
than 100mbit with the hardware I have, sorry).

Note that I haven't done tests at 100mbit on this setup before, so can't
say whether something weird is going on there. I'm a little bit puzzled
as to why the flows don't seem to get going at all in one direction for
the rrul test. I'm guessing it has something to do with TSQ.

Attaching graphs makes the listserv bounce my mail, so instead they're
here: http://archive.tohojo.dk/bufferbloat-data/long-rtt/ with
throughput data below. Overall, it looks pretty good for fq_codel I'd
say :)

I can put up the data files as well if you'd like.

-Toke


Throughput data:


10mbit:

rrul test (4 flows each way), pfifo_fast qdisc:
 TCP download sum:
  Data points: 299
  Total:       375.443728 Mbits
  Mean:        6.278323 Mbits/s
  Median:      6.175466 Mbits/s
  Min:         0.120000 Mbits/s
  Max:         9.436373 Mbits/s
  Std dev:     1.149514
  Variance:    1.321382
--
 TCP upload sum:
  Data points: 300
  Total:       401.740454 Mbits
  Mean:        6.695674 Mbits/s
  Median:      6.637576 Mbits/s
  Min:         2.122827 Mbits/s
  Max:         16.892302 Mbits/s
  Std dev:     1.758319
  Variance:    3.091687

  
rrul test (4 flows each way), fq_codel qdisc:
 TCP download sum:
  Data points: 301
  Total:       492.824346 Mbits
  Mean:        8.186451 Mbits/s
  Median:      8.416901 Mbits/s
  Min:         0.120000 Mbits/s
  Max:         9.965051 Mbits/s
  Std dev:     1.244959
  Variance:    1.549924
--
 TCP upload sum:
  Data points: 305
  Total:       717.499994 Mbits
  Mean:        11.762295 Mbits/s
  Median:      8.630924 Mbits/s
  Min:         2.513799 Mbits/s
  Max:         323.180000 Mbits/s
  Std dev:     31.056047
  Variance:    964.478066


TCP test (one flow each way), pfifo_fast qdisc:
 TCP download:
  Data points: 301
  Total:       263.445418 Mbits
  Mean:        4.376170 Mbits/s
  Median:      4.797729 Mbits/s
  Min:         0.030000 Mbits/s
  Max:         5.757982 Mbits/s
  Std dev:     1.135209
  Variance:    1.288699
---
 TCP upload:
  Data points: 302
  Total:       321.090853 Mbits
  Mean:        5.316074 Mbits/s
  Median:      5.090142 Mbits/s
  Min:         0.641123 Mbits/s
  Max:         24.390000 Mbits/s
  Std dev:     2.126472
  Variance:    4.521882


TCP test (one flow each way), fq_codel qdisc:
 TCP download:
  Data points: 302
  Total:       365.357123 Mbits
  Mean:        6.048959 Mbits/s
  Median:      6.550488 Mbits/s
  Min:         0.030000 Mbits/s
  Max:         9.090000 Mbits/s
  Std dev:     1.316275
  Variance:    1.732579
---
 TCP upload:
  Data points: 303
  Total:       466.550695 Mbits
  Mean:        7.698856 Mbits/s
  Median:      6.144435 Mbits/s
  Min:         0.641154 Mbits/s
  Max:         127.690000 Mbits/s
  Std dev:     12.075298
  Variance:    145.812812


100 mbit:

rrul test (4 flows each way), pfifo_fast qdisc:
 TCP download sum:
  Data points: 301
  Total:       291.718140 Mbits
  Mean:        4.845816 Mbits/s
  Median:      4.695355 Mbits/s
  Min:         0.120000 Mbits/s
  Max:         10.774475 Mbits/s
  Std dev:     1.818852
  Variance:    3.308222
--
 TCP upload sum:
  Data points: 305
  Total:       5468.339961 Mbits
  Mean:        89.644917 Mbits/s
  Median:      90.731214 Mbits/s
  Min:         2.600000 Mbits/s
  Max:         186.362429 Mbits/s
  Std dev:     21.782436
  Variance:    474.474532


rrul test (4 flows each way), fq_codel qdisc:
 TCP download sum:
  Data points: 304
  Total:       427.064699 Mbits
  Mean:        7.024090 Mbits/s
  Median:      7.074768 Mbits/s
  Min:         0.150000 Mbits/s
  Max:         17.870000 Mbits/s
  Std dev:     2.079303
  Variance:    4.323501
--
 TCP upload sum:
  Data points: 305
  Total:       5036.774674 Mbits
  Mean:        82.570077 Mbits/s
  Median:      82.782532 Mbits/s
  Min:         2.600000 Mbits/s
  Max:         243.990000 Mbits/s
  Std dev:     22.566052
  Variance:    509.226709


TCP test (one flow each way), pfifo_fast qdisc:
 TCP download:
  Data points: 160
  Total:       38.477172 Mbits
  Mean:        1.202412 Mbits/s
  Median:      1.205256 Mbits/s
  Min:         0.020000 Mbits/s
  Max:         4.012585 Mbits/s
  Std dev:     0.728299
  Variance:    0.530419
 TCP upload:
  Data points: 165
  Total:       2595.453489 Mbits
  Mean:        78.650106 Mbits/s
  Median:      92.387832 Mbits/s
  Min:         0.650000 Mbits/s
  Max:         102.610000 Mbits/s
  Std dev:     30.432215
  Variance:    926.119728



TCP test (one flow each way), fq_codel qdisc:
  Data points: 301
  Total:       396.307606 Mbits
  Mean:        6.583183 Mbits/s
  Median:      7.786816 Mbits/s
  Min:         0.030000 Mbits/s
  Max:         15.270000 Mbits/s
  Std dev:     3.034477
  Variance:    9.208053
 TCP upload:
  Data points: 302
  Total:       4238.768131 Mbits
  Mean:        70.178280 Mbits/s
  Median:      74.722554 Mbits/s
  Min:         0.650000 Mbits/s
  Max:         91.901862 Mbits/s
  Std dev:     17.860375
  Variance:    318.993001


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-07-08 17:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 19:33 Dave Taht
2013-07-04  5:57 ` Mikael Abrahamsson
2013-07-04 13:51   ` Michael Richardson
2013-07-04 15:48     ` Mikael Abrahamsson
2013-07-07 18:52   ` dpreed
2013-07-08  0:24     ` Mikael Abrahamsson
2013-07-08 17:03       ` Toke Høiland-Jørgensen [this message]
2013-07-09  3:24         ` Dave Taht
2013-07-09  6:04         ` Mikael Abrahamsson
2013-07-09  6:32           ` Dave Taht
2013-07-09  7:30             ` [Cerowrt-devel] [Codel] " Andrew McGregor
2013-07-09 13:09             ` Eric Dumazet
2013-07-09  7:57           ` [Cerowrt-devel] " Toke Høiland-Jørgensen
2013-07-09 12:56             ` [Cerowrt-devel] [Codel] " Eric Dumazet
2013-07-09 13:13               ` Toke Høiland-Jørgensen
2013-07-09 13:23                 ` Eric Dumazet
2013-07-09 13:25                   ` Toke Høiland-Jørgensen
2013-07-09 13:36                 ` Eric Dumazet
2013-07-09 13:45                   ` Toke Høiland-Jørgensen
2013-07-09 13:49                     ` Eric Dumazet
2013-07-09 13:53                       ` Toke Høiland-Jørgensen
2013-07-09 14:07                         ` Eric Dumazet
2013-07-08 20:50       ` [Cerowrt-devel] " dpreed
2013-07-08 21:04         ` Jim Gettys
2013-07-09  5:48         ` Mikael Abrahamsson
2013-07-09  5:58           ` dpreed

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

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

  git send-email \
    --in-reply-to=871u79x9kb.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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