From: Aaron Wood <woody77@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: Richard Smith <smithbone@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Linksys wrt1900acs rrul traces
Date: Thu, 07 Apr 2016 20:36:53 +0000 [thread overview]
Message-ID: <CALQXh-MkZvxbviC7gE7EKBuUK4cFPLNFiXjfTAomZLRNHO11RQ@mail.gmail.com> (raw)
In-Reply-To: <DC87914F-09C2-415E-AA16-558933E8E374@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 3525 bytes --]
Or I can't read properly... I have the first gen wrt1900ac. Dual-core
1.2GHz arm.
-Aaron
On Thu, Apr 7, 2016 at 10:50 moeller0 <moeller0@gmx.de> wrote:
> Hi Aaron,
>
>
> On Apr 7, 2016, at 19:42 , Aaron Wood <woody77@gmail.com> wrote:
>
> These are really impressive results (flent graphs attached for the
> "simple" operation).
>
> Especially so, considering to what I see with sqm_scripts on the same
> hardware with CCrc3:
> http://burntchrome.blogspot.com/2015/06/sqmscripts-before-and-after-at-160mbps.html
>
>
> Richard has an wrt1900acs (https://wikidevi.com/wiki/Linksys_WRT1900ACS),
> while I believe you have an wrt1900AC (
> https://wikidevi.com/wiki/Linksys_WRT1900AC) so Richard’s seems a bit
> more recent and powerful. Or I am an idiot and can not read properly…
>
> Best Regards
> Sebastian
>
>
> Is this stable enough for full-time usage (as a home router)?
>
> -Aaron
>
> On Thu, Apr 7, 2016 at 6:58 AM, Richard Smith <smithbone@gmail.com> wrote:
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
>
>
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 5603 bytes --]
[-- Attachment #2: dd_simple.all.png --]
[-- Type: image/png, Size: 105604 bytes --]
[-- Attachment #3: dd_simple.cdf.png --]
[-- Type: image/png, Size: 54360 bytes --]
next prev parent reply other threads:[~2016-04-07 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:58 Richard Smith
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 [this message]
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=CALQXh-MkZvxbviC7gE7EKBuUK4cFPLNFiXjfTAomZLRNHO11RQ@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=smithbone@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