Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Tue, 7 Jul 2015 18:48:11 -0600	[thread overview]
Message-ID: <CAK-n8j7GVG-h0ZKh7mdc8K2u5=P9g18dZfDbkwGpi0BCeL-R_A@mail.gmail.com> (raw)
In-Reply-To: <ACB21509-F29C-4004-8ACE-D5BEC822DA8A@gmail.com>

On Mon, Jul 6, 2015 at 8:23 PM, Rich Brown wrote:

> The WNDR3800 remains our gold standard for CeroWrt builds. It'll do SQM up to ~30 mbps, then the CPU runs out of gas.

Could someone on this list please quantify what "the CPU runs out of
gas" means?  Is this when steaming full-bandwidth?  What happens when
this threshold is reached?

I'm concerned because my Comcast service runs at 60 Mbps (nominal),
and we have been having some intermittent glitches with Netflix.  I'm
running the last CeroWrt release that Dave Taht published, with
default SQM profile enabled.  In the interest of family harmony, I've
never sat in front of the TV while watching the real-time status on
the router, to see if it's even getting close to or going over 30
Mbps.  There's usually little else happening on the LAN while Netflix
is on.

If I am saturating the router (SQM), I'd like to find a better HW
solution.  However, it seems like getting CeroWRT going on the various
Linksys AC1200/1900 models is not as straightforward as on the
WNDR3800.

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

  parent reply	other threads:[~2015-07-08  0:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:02 Joe Touch
2015-07-07  2:23 ` Rich Brown
2015-07-07  4:22   ` Joe Touch
2015-07-07  7:20     ` Sebastian Moeller
2015-07-07 12:03       ` [Cerowrt-devel] [Bloat] " Kevin Darbyshire-Bryant
2015-07-07 14:07     ` [Cerowrt-devel] " Rich Brown
2015-07-07 18:19       ` Matt Taggart
2015-07-08  1:54         ` Rich Brown
2015-07-08 18:37         ` Joe Touch
2015-07-08 20:15           ` Sebastian Moeller
2015-07-08 20:28             ` Joe Touch
2015-07-08 22:16               ` Sebastian Moeller
2015-07-09  1:34                 ` Rich Brown
2015-07-08  0:48   ` Jim Reisert AD1C [this message]
2015-07-08  2:47     ` Dave Taht
2015-07-07  6:16 ` Mikael Abrahamsson
2015-07-07 18:34   ` Joe Touch
2015-07-10  7:03     ` Mikael Abrahamsson
2015-07-10  7:22       ` Joe Touch
2015-07-10  7:48         ` Mikael Abrahamsson
2015-07-10  8:01         ` Sebastian Moeller
2015-07-10 16:57           ` Joe Touch
2015-07-07 15:40 ` Dave Taht

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='CAK-n8j7GVG-h0ZKh7mdc8K2u5=P9g18dZfDbkwGpi0BCeL-R_A@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --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