From: dpreed@reed.com
To: "Dave Taht" <dave@taht.net>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] 1Gbit/20Mbit D/L with ack-filtering
Date: Wed, 29 Nov 2017 17:34:06 -0500 (EST) [thread overview]
Message-ID: <1511994846.127314610@apps.rackspace.com> (raw)
In-Reply-To: <87vahuxgt9.fsf@nemesis.taht.net>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Very interesting. The aggressive-ack-filter seems to mess throughput up during "boost phase" compared to ack-filter less agreesive.
I should say that my most common heavy upload/download usage has an RTT of 88 msec. (Boston - AWS west).
Personal heavy upload/download usage is has RTT of about 24 msec. (github, my two personal cloud servers).
I wonder if 88 and 25 msec RTT are much better in practice. I will be testing cake in a week or so (delay due to family converging on me due to my daughter's wedding).
BTW, one annoying thing about flent is that netperf is not available in fedora, rhel, centos as a package. So I have to install it and it doesn't just plug in smoothly. That's just my convenience issue. I don't use netperf myself on any of my systems. iperf and iperf3 seem to be a lot more pervasive these days...
On Tuesday, November 28, 2017 3:57pm, "Dave Taht" <dave@taht.net> said:
>
> Wrote up that result here:
>
> http://blog.cerowrt.org/post/ack_filtering/
>
[-- Attachment #2: Type: text/html, Size: 2341 bytes --]
next prev parent reply other threads:[~2017-11-29 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 20:57 Dave Taht
2017-11-29 22:34 ` dpreed [this message]
2017-11-29 22:43 ` 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=1511994846.127314610@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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