From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] AWS, fq_codel, and... tcp illinois?
Date: Sat, 18 Jun 2016 16:30:07 -0700 [thread overview]
Message-ID: <CAA93jw5-EGgDXRD4dgB1aeVPcG_MfCRfsu9QaXGYvgiqZzbYEg@mail.gmail.com> (raw)
As seen on page 35 of..
media.amazonwebservices.com/jp/summit2016/2D-01.pdf
page 49 shows a 32% improvement on the "apache ab" benchmark.
This preso is in japanese, if there is anything else interesting about
it, let me know....
using google translate:
All default 2,164Mbps 30.4 seconds
Doubling the TCP buffer on the server side 1,780Mbps 37.4 seconds
Doubling the client-side TCP buffer of 2,462Mbps 27.6 seconds
Active queue management on the server side 2,249Mbps 29.3 seconds
Client buffer + AQM 2,730Mbps 24.5 seconds
Illinois CC + client buffer + AQM 2,847Mbps 23.0 seconds
Illinois CC + server / client buffer + AQM 2,865Mbps 23.5 seconds
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
reply other threads:[~2016-06-18 23:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5-EGgDXRD4dgB1aeVPcG_MfCRfsu9QaXGYvgiqZzbYEg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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