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>
Subject: Re: [Cake] ack filter rrul result at 1000/100
Date: Wed, 15 Nov 2017 19:45:52 -0800	[thread overview]
Message-ID: <CAA93jw7H9YsrXAqq-aAb55s715FfR35MVbt35S6mFyU+DjNWFQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw50mhOUOR7cnicjC2KSx65BqUqXFnZtJBc2fe_O_4C8Vg@mail.gmail.com>

Please disregard that result entirely, my test setup was wrong and I
jumped for joy too early.

(turned out on the second run I'd rate limited the wrong interface
also to 100mbit)

On Wed, Nov 15, 2017 at 7:13 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I pulled together rmounce's patchset for ack filtering and my own
> ongoing netem work and had a chance to run a few tests.
>
> Pretty remarkable. The attached graph is a 1gbit (unshaped) link up
> with a 100Mbit down, the classic rrul 4 upload and 4 download flows,
> with the ping measurement....
>
> Just an across the board win, unless the tcp gods rain hellfire down
> on us. And wow, look at all those acks that got killed.
>
>  backlog 0b 0p requeues 1
>  memory used: 317312b of 5000000b
>  capacity estimate: 100Mbit
>                  Bulk   Best Effort      Voice
>   thresh      6250Kbit     100Mbit      25Mbit
>   target         5.0ms       5.0ms       5.0ms
>   interval     100.0ms     100.0ms      10.0ms
>   pk_delay         2us        10us        53us
>   av_delay         1us         1us         4us
>   sp_delay         1us         1us         3us
>   pkts          228783     1937474      631425
>   bytes      104982588  1189472341   380759260
>   way_inds           0           0           0
>   way_miss           6          63          19
>   way_cols           0           0           0
>   drops           6076        2091        1993
>   marks              0           0           0
>   ack_drop       67510      135880      102528
>   sp_flows           0           1           0
>   bk_flows           0           0           1
>   un_flows           0           0           0
>   max_len         6056       15140       10598
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619



-- 

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

  reply	other threads:[~2017-11-16  3:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  3:13 Dave Taht
2017-11-16  3:45 ` Dave Taht [this message]
2017-11-16  4:28   ` Dave Taht
2017-11-16 11:30     ` Sebastian Moeller
2017-11-16 13:55     ` Bret Towe
2017-11-16 14:29       ` Sebastian Moeller
2017-11-16 14:33         ` Bret Towe
2017-11-16 15:03       ` Jonathan Morton
2017-11-16 16:25         ` Dave Taht
     [not found] <mailman.1021.1510806526.3609.cake@lists.bufferbloat.net>
2017-11-16  9:24 ` Pete Heist
2017-11-16 12:47   ` Alan Jenkins

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=CAA93jw7H9YsrXAqq-aAb55s715FfR35MVbt35S6mFyU+DjNWFQ@mail.gmail.com \
    --to=dave.taht@gmail.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