Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Comcast upped service levels -> WNDR3800 can't cope...
Date: Fri, 29 Aug 2014 19:25:14 +0200	[thread overview]
Message-ID: <11CF384A-59DD-4352-B8EA-F2F714182AF9@gmx.de> (raw)
In-Reply-To: <CALQXh-Pkqh6Wq9xc9ky0ruztu74ziUoiaiG0LPr+DVLtDqz4mQ@mail.gmail.com>

Hi Aaron,


On Aug 29, 2014, at 18:57 , Aaron Wood <woody77@gmail.com> wrote:

> Comcast has upped the download rates in my area, from 50Mbps to 100Mbps.  This morning I tried to find the limit of the WNDR3800.  And I found it.  50Mbps is still well within capabilities, 100Mbps isn't.
> 
> And as I've seen Dave say previously, it's right around 80Mbps total (download + upload).
> 
> http://burntchrome.blogspot.com/2014/08/new-comcast-speeds-new-cerowrt-sqm.html
> 
> I tried disabling downstream shaping to see what the result was, and it wasn't pretty.

	You could try to set the interface to 100Mbps with ethtool and exercise cerowrt BQL implementation a bit ;)

>  I also tried using the "simplest.qos" script, and that didn't really gain me anything, so I went back to the simple.qos script (those results aren't included above).
> 
> It looks like it's definitely time for a new router platform (for me).
> 
> Or, we need to find a way to implement the system such that it doesn't max out a 680MHz mips core just to push 100Mbps of data.  That's roughly 10K cpu cycles per packet, which seems like an awful lot.  Unless the other problem is that the memory bus just can't keep up.  My experience of a lot of these processors is that the low-level offload engines have great DMA capabilities for "wire-speed" operation, but that the processor core itself can't move data to save it's life.

	Could you try simplest.qos and replace HTB with TBF? We still do not know whether there is a cheaper option than HTB that still works okay-ish (I only have 16D 2U, so can not easily test myself). I guess that TBF is just as expensive as HTB since both shaw more or less the same token bucket algorithm...

> 
> What's the limit of the EdgeRouter Lite?

	I think this tops out at ~ 80-90Mbps combined, but there is no BQL yet. Given the price of tho unit it would be really nice if that would work for the 150-200Mbps combined that seem to be needed in the near future.

> 
> Or should I start looking for something like this:
> 
> http://www.gateworks.com/product/item/ventana-gw5310-network-processor
> 
> (although that's an expensive board, given the very low production volume, for the same cost I could probably build a small passively-cooled mini/micro-atx setup running x86 and dual NICs).
> 
> -Aaron
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  parent reply	other threads:[~2014-08-29 17:25 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 16:57 [Cerowrt-devel] " Aaron Wood
2014-08-29 17:03 ` [Cerowrt-devel] [Bloat] " Rick Jones
2014-08-29 17:15 ` Jonathan Morton
2014-08-29 17:19 ` Jonathan Morton
2014-08-29 17:25 ` Sebastian Moeller [this message]
2014-08-29 18:06 ` Dave Taht
2014-08-30 11:02   ` Jonathan Morton
2014-08-30 13:03     ` Toke Høiland-Jørgensen
2014-08-30 17:33       ` Jonathan Morton
2014-08-30 20:47         ` Jonathan Morton
2014-08-30 22:30           ` Dave Taht
2014-08-31 10:18             ` Jonathan Morton
2014-08-31 10:21               ` Toke Høiland-Jørgensen
2014-09-01 17:01               ` Dave Taht
2014-09-01 18:06                 ` Jonathan Morton
2014-09-01 18:32                   ` Dave Taht
2014-09-01 20:25                     ` Aaron Wood
2014-09-01 21:43                       ` Jonathan Morton
2014-09-01 22:14                         ` Aaron Wood
2014-09-02  9:09                           ` David Lang
2014-09-02  9:27                           ` Jonathan Morton
2014-09-02 10:05                             ` Joel Wirāmu Pauling
2014-09-02 10:05                               ` Joel Wirāmu Pauling
2014-09-03  6:15                           ` Aaron Wood
2014-09-03  6:36                             ` David Lang
2014-09-03 11:08                             ` Jonathan Morton
2014-09-03 15:12                               ` Aaron Wood
2014-09-03 19:22                                 ` Sebastian Moeller
2014-09-03 19:30                                   ` Dave Taht
2014-09-03 23:17                                     ` Bill Ver Steeg (versteb)
2014-09-04  0:33                                       ` Dave Taht
2014-09-04  3:36                                         ` Jonathan Morton
2014-09-04 14:05                                         ` Bill Ver Steeg (versteb)
2014-09-04 15:10                                       ` Michael Richardson
2014-09-04  7:04                                     ` Sebastian Moeller
2014-09-04 11:15                                       ` Jonathan Morton
2014-09-04 11:23                                         ` Sebastian Moeller
2014-09-02  8:55                         ` Sebastian Moeller
2014-09-02 13:40                     ` Jonathan Morton
2014-09-02 13:49                       ` Sujith Manoharan
2014-09-02 15:37                       ` Dave Taht
2014-09-02 15:47                         ` Jonathan Morton
2014-09-02 15:57                           ` Sujith Manoharan
2014-09-02 17:36                         ` Jonathan Morton
2014-09-02 17:41                           ` Dave Taht
2014-09-02 18:28                             ` Jonathan Morton
2014-09-03 11:04                         ` Jonathan Morton
2014-08-30 21:53     ` Stephen Hemminger
2014-08-30 11:14   ` Jonathan Morton
2014-08-30 17:19   ` Aaron Wood
2014-08-30 18:01     ` Jonathan Morton
2014-08-30 18:21     ` Sebastian Moeller

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=11CF384A-59DD-4352-B8EA-F2F714182AF9@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@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