From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] sqm-scripts on WRT1900AC
Date: Sat, 23 May 2015 22:17:46 -0700 [thread overview]
Message-ID: <CALQXh-PeerhPiWEhqWdGtrHN-fDMuQzObsCXq=83k+644yRSEg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
All,
I've been lurking on the OpenWRT forum, looking to see when the CC builds
for the WRT1900AC stabilized, and they seem to be so (for a very "beta"-ish
version of stable).
So I went ahead and loaded up the daily ( CHAOS CALMER (Bleeding Edge,
r45715)).
After getting Luci and sqm-scripts installed, I did a few baseline tests.
Wifi to the MacBook Pro is... broken. 30Mbps vs. 90+ on the stock
firmware. iPhone is fine (80-90Mbps download speed from the internet).
After some rrul runs, this is what I ended up with:
http://www.dslreports.com/speedtest/538967
sqm-scripts are set for:
100Mbps download
10Mbps upload
fq_codel
ECN
no-squash
don't ignore
Here's a before run, with the stock firmware:
http://www.dslreports.com/speedtest/337392
So, unfortunately, it's still leaving 50Mbps on the table.
However, if I set the ingress limit higher (130Mbps), buffering is still
controlled. Not as well, though. from +5ms to +10ms, with lots of
jitter. But it still looks great to the dslreports test:
http://www.dslreports.com/speedtest/538990
But the upside? load is practically nil. The WRT1900AC, with it's
dual-core processor is more than enough to keep up with this (from a load
point of view), but it seems like the bottleneck isn't the raw CPU power
(cache?).
I'll get a writeup with graphs on the blog tomorrow (I hope).
-Aaron
[-- Attachment #2: Type: text/html, Size: 1960 bytes --]
next reply other threads:[~2015-05-24 5:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 5:17 Aaron Wood [this message]
2015-05-24 6:19 ` Aaron Wood
2015-05-25 23:55 ` [Cerowrt-devel] [Bloat] " David Lang
2015-05-29 8:34 ` Pedro Tumusok
2015-05-29 9:09 ` David Lang
2015-05-29 10:04 ` Pedro Tumusok
2015-05-29 20:26 ` David Lang
2015-06-01 8:47 ` Pedro Tumusok
2015-05-24 6:44 ` Dave Taht
2015-05-24 6:51 ` Aaron Wood
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-PeerhPiWEhqWdGtrHN-fDMuQzObsCXq=83k+644yRSEg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@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