Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Bret Towe <bret.towe@gmail.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] ack filter rrul result at 1000/100
Date: Thu, 16 Nov 2017 15:29:17 +0100	[thread overview]
Message-ID: <A031849D-2481-4247-8F07-C8A1DD934C49@gmx.de> (raw)
In-Reply-To: <CAM+OQmBjXe6=-TOjA=FMd4HPByrhWseheO=AOpjFR19Ow8Kctw@mail.gmail.com>


> On Nov 16, 2017, at 14:55, Bret Towe <bret.towe@gmail.com> wrote:
> 
> I have a docsis setup atm that is 300/7

300/7 = 42.9/1

This is extreme, I do not envy you at all. I would venture a guess that your ISP would be a prime candidate for doing ACK filtering/thinning in its CPE. Is there an easy way to compare sent versus received ACKs over the internet?

Best Regards


> 
> 
> On Nov 15, 2017 8:28 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
> This is a much saner test result[1], showing about a 20% improvement
> under the rrul_be test. I scaled back the topology to two instances of
> cake on the middlebox, shaping to 100mbits on one side and 10mbits on
> the other, and flipped filtering on or off. The win will improve more
> with upload/download ratios of ever worse than 10/1, and the rrul is
> not exactly a test of real traffic.
> 
> What other ratios are out there, particularly in the dsl world?
> 
> I can think of a few ways to get more acks to filter out, for example,
> not using the "sparse flow optimization" for acks.
> 
> [1] it also turned out my test target box, an odroid c2, couldn't push
> more than 500mbits bidir in the first place.
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  reply	other threads:[~2017-11-16 14:29 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
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 [this message]
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=A031849D-2481-4247-8F07-C8A1DD934C49@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bret.towe@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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