From: "Richard A. Smith" <richard@laptop.org>
To: Dave Taht <dave.taht@gmail.com>, David Lang <david@lang.hm>
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, 05 Oct 2014 12:26:01 -0400 [thread overview]
Message-ID: <54317119.2090605@laptop.org> (raw)
In-Reply-To: <CAA93jw5Sc0ujnwv-foPQ=iD5Jgfi08RTOR4OCd4t_qbuJ6i2mg@mail.gmail.com>
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.
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.
--
Richard A. Smith <richard@laptop.org>
Former One Laptop per Child
next prev parent reply other threads:[~2014-10-05 16:26 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 [this message]
2014-10-05 17:57 ` Dave Taht
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=54317119.2090605@laptop.org \
--to=richard@laptop.org \
--cc=alphasparc@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--cc=openwrt-devel@lists.openwrt.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