From: Richard Smith <smithbone@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Linksys wrt1900acs rrul traces
Date: Thu, 7 Apr 2016 09:58:43 -0400 [thread overview]
Message-ID: <57066793.5050608@gmail.com> (raw)
A while ago I mentioned that I purchased a Linksys wrt1900acs and I was
going to do some comparisons of speed/rrul for stock firmware and stuff
running sqm.
It took a while to happen but I finally got it done. I was stalled for
a long time because for a while OpenWRT was not complete for this
router. It would boot but you could not (easily) return to the factory
firmware as updates via the OpenWRT web interface did not work.
Command line updates still worked though periodically I would build dd
head and see if it got fixed. Finally one weekend I decided to dig in
and figure out what was going wrong and discovered that someone else
beat me to it and it all was working now.
The following flent rrul runs were run here on my local Gbit network
(pretty quiet) using with OpenWrt Designated Driver r49051 / LuCI Master
(git-16.081.38806-6b9a743) + Cake installed.
Cake installed via the instructions here:
http://www.bufferbloat.net/projects/codel/wiki/Cake#Installing-CAKE-out-of-tree-on-OpenWrt-rough-instructions
For these tests I had the inbound and outbound limits set to 975000
kbps. 975000 was somewhat arbitrary. I wanted it below 1Gbps enough
that I could be sure it was the router as the limit but yet fast enough
that I would be able to see the peak transfer rates.
Test setup is:
Laptop<-->wrt1900acs<--->Gbit Switch<--->Netperf server
Prior to running the tests I did trial runs without the wrt1900acs in
the chain to verify every thing worked at Gbit speeds.
I ran the rrul test for each of the SQM settings at least 5 times. For
layer cake and piece of cake each had a run with results that were way
off from the previous run. I'm assuming this is some yet to be fixed
issue and so I ran it 1 more time so that there were 5 runs with similar
results.
All the raw files are in this tarball:
https://drive.google.com/file/d/0B-P0wCbNmKvAWmRUSzNMdXpUOFE/view?usp=sharing
Hope this is helpful. I'll be happy to run any additional tests if
someone wants more.
--
Richard A. Smith
next reply other threads:[~2016-04-07 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:58 Richard Smith [this message]
2016-04-07 15:24 ` Dave Taht
2016-04-08 11:51 ` Richard Smith
2016-04-07 16:16 ` moeller0
2016-04-07 16:40 ` Dave Taht
2016-04-08 11:51 ` Richard Smith
2016-04-08 13:17 ` Sebastian Moeller
2016-04-08 13:55 ` John Yates
2016-04-08 19:20 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces ko Sebastian Moeller
2016-04-07 17:42 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces Aaron Wood
2016-04-07 17:48 ` Dave Taht
2016-04-07 17:50 ` moeller0
2016-04-07 18:05 ` Dave Taht
2016-04-07 20:36 ` Aaron Wood
2016-04-08 11:51 ` Richard Smith
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=57066793.5050608@gmail.com \
--to=smithbone@gmail.com \
--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