Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Richard A. Smith" <richard@laptop.org>
Cc: Alpha Sparc <alphasparc@gmail.com>,
	openwrt-devel <openwrt-devel@lists.openwrt.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] better ingress shaping somehow
Date: Sun, 5 Oct 2014 10:57:11 -0700	[thread overview]
Message-ID: <CAA93jw5JS7WpAzxSnbwWyR+10Bwmrga0O2V2SgbEvwgHduUFeA@mail.gmail.com> (raw)
In-Reply-To: <54317119.2090605@laptop.org>

On Sun, Oct 5, 2014 at 9:26 AM, Richard A. Smith <richard@laptop.org> wrote:
> On 10/02/2014 07:07 PM, Dave Taht wrote:
>
>>> I beleive that on the WNDR3800, it's able to work up to about 50Mb with
>>> the
>>> existing configurations. A faster CPU would do better, a slower one
>>> worse.
>>
>>
>> Actually it appears that cache is very important on fixing inbound rate
>> shaping.
>>
>> The octeon in the edgerouter lite peaks out at above 60mbits also, but the
>> bigger, fatter pro product actually manages quite a bit better (with
>> increasing
>> inaccuracy however). See below...
>
>
> Ugh.  Got any hard numbers on the top speed of the edgerouter with shaping?
>
> At work we recently upgraded our link from 60/10 to 100/15 and the WNDR I
> have running the show can no longer keep up.  I've been looking for a
> replacement and the edgerouter lite was looking like a possibility.

Shaping the uplink only still helps a lot.

> I tried to use a TPLink AC1750 thinking that a newer setup with a faster cpu
> might be able to keep up.  If I don't have shaping enabled it can do 200+
> Mbit but with shaping it drops considerably.  It's still faster than the
> WNDR but seems to max out at about 85 Mbit.

The fastest-looking thing I've played with of late is the netgear x4.
It's dynamic QoS feature
is basically fq_codel, near as I can tell. I'll try pushing it to
120Mbit this week.

I do not have a high impression of it's overall firmware quality, and
haven't seen the gpl drop yet.

Aside from that, there's always x86.

> --
> Richard A. Smith  <richard@laptop.org>
> Former One Laptop per Child



-- 
Dave Täht

https://www.bufferbloat.net/projects/make-wifi-fast

  reply	other threads:[~2014-10-05 17:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 23:07 Dave Taht
2014-10-03  0:57 ` William Katsak
2014-10-03  1:26   ` Dave Taht
2014-10-03 18:02 ` Sebastian Moeller
2014-10-05 16:26 ` Richard A. Smith
2014-10-05 17:57   ` Dave Taht [this message]
2014-10-06  2:16     ` Richard A. Smith
2014-10-06  2:37       ` Richard A. 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=CAA93jw5JS7WpAzxSnbwWyR+10Bwmrga0O2V2SgbEvwgHduUFeA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=alphasparc@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=richard@laptop.org \
    /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