Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>
Subject: [Cake] cake at 3gbit
Date: Wed, 30 May 2018 14:32:10 -0700	[thread overview]
Message-ID: <CAA93jw4cOmpSu=BCxEyY2_cW28YZmBQ-uVqyphwEwezOiAmXcA@mail.gmail.com> (raw)

my old veth code - which simulates 5 hops - can only achieve about
4gbit on the hardware I have with netem on a 20ms delay. There are
undoubtably other bottlenecks elsewhere in the system in this
configuration. :)

I DO have real 10GigE hardware now, but would love to see someone
trying cake at 40GigE+ in the real world now that it allows
superpackets and the api allows for more than 40Gbit to be specified.

regretably, hit a bug, we need to wait for toke's v18 to come out.

At 3gbit, with netem inserting 10ms delay in each direction, it's hard
to complain.


root@spaceheater:~/git/veth# ip netns exec client flent -H 10.10.0.1
-t cake-3gbit rrul_be
Started Flent 1.1.1-git-5daa2b3 using Python 3.5.2.
Starting rrul_be test. Expected run time: 70 seconds.
Data file written to ./rrul_be-2018-05-30T142933.502257.cake-3gbit.flent.gz.
Summary of rrul_be test run 'cake-3gbit' (at 2018-05-30 21:29:33.502257):

                              avg       median          # data pts
 Ping (ms) ICMP    :        20.32        20.30 ms              349
 Ping (ms) UDP BE1 :        48.84        20.48 ms              342
 Ping (ms) UDP BE2 :        48.84        20.48 ms              342
 Ping (ms) UDP BE3 :        48.84        20.48 ms              342
 Ping (ms) avg     :        41.71        20.43 ms              351
 TCP download BE   :       704.57       705.27 Mbits/s         300
 TCP download BE2  :       700.29       705.23 Mbits/s         300
 TCP download BE3  :       703.67       705.24 Mbits/s         299
 TCP download BE4  :       700.28       705.28 Mbits/s         300
 TCP download avg  :       702.20       705.09 Mbits/s         301
 TCP download sum  :      2808.81      2820.35 Mbits/s         301
 TCP totals        :      5615.83      5640.44 Mbits/s         301
 TCP upload BE     :       704.32       705.66 Mbits/s         286
 TCP upload BE2    :       703.59       705.46 Mbits/s         286
 TCP upload BE3    :       699.39       705.29 Mbits/s         286
 TCP upload BE4    :       699.72       705.38 Mbits/s         285
 TCP upload avg    :       701.75       705.08 Mbits/s         301
 TCP upload sum    :      2807.02      2820.31 Mbits/s         301


-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

             reply	other threads:[~2018-05-30 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 21:32 Dave Taht [this message]
2018-05-31 15:40 ` Toke Høiland-Jørgensen

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

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

  git send-email \
    --in-reply-to='CAA93jw4cOmpSu=BCxEyY2_cW28YZmBQ-uVqyphwEwezOiAmXcA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=brouer@redhat.com \
    --cc=cake@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