From: Dave Taht <dave.taht@gmail.com>
To: Ernesto Elias <ernestogelias@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Routing limit question
Date: Sun, 19 Oct 2014 12:41:15 -0700 [thread overview]
Message-ID: <CAA93jw6VvtLAMN-TwVdj+2SX9V7Xg8RN9B9LaB8SqPmUhQY+nA@mail.gmail.com> (raw)
In-Reply-To: <CAAMzHDaq1+f8fE1igfqzR4mMJES=fjBF1CAq82RuL3srwZ8DPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3424 bytes --]
Sorry there are two conversational threads here on hynyman s thread they
are benchmarking vs an anctiontec.
Also it does seem like fiddling with the burst parameter to htb seems
warrented.
On Oct 19, 2014 12:33 PM, "Ernesto Elias" <ernestogelias@gmail.com> wrote:
> I'm not using the actiontec at all. I'm using the wndr3800
> On Oct 19, 2014 3:22 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
>
>> It looks to me as if the actiontec has pretty good qos all by itself.
>> On Oct 19, 2014 11:56 AM, "Sebastian Moeller" <moeller0@gmx.de> wrote:
>>
>>> HI Dave,
>>>
>>>
>>> On Oct 19, 2014, at 20:24 , Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> > On at least one verizon device I've tried it appeared that they had
>>> > SFQ or something similar on egress from the modem.
>>> >
>>> >
>>> http://www.bufferbloat.net/projects/codel/wiki/RRUL_Rogues_Gallery#Verizon-FIOS-Testing-at-25Mbit-up-and-25Mbit-down
>>> >
>>> > So you only needed to shape the download. which is good as we start
>>> > peaking out at 50Mbit download total. But only measurements can tell.
>>>
>>> So on Hnymans community openwrt build a few fortunate ones on
>>> excellent lines seem to get decent results even at 110-120 Mbps combined:
>>> https://forum.openwrt.org/viewtopic.php?pid=250989#p250989
>>> and:
>>> https://forum.openwrt.org/viewtopic.php?pid=251013#p251013
>>> I have no idea why and both lines were reasonably well-behaved even
>>> without any AQM/QOS...
>>>
>>> Also I wonder whether when we increase the quantum for higher rates to
>>> give HTB some breathing room, whether we also should increase burst and
>>> cburst? My hunch is that quantum affects the switching between the leaves,
>>> while busts and cburst should allow to dump more data to lower layers
>>> inside each leaf qdisc. And since we are running behind, maybe taking a
>>> bigger shovel can help some. (I assume this needs to be titrated not to
>>> kill latency under load, but if we can only effective have HTB execute x
>>> times per second we can easily afford to dump
>>> line-rate/maxHTB_iteratin_rate bytes per opportunity, no?) My own internet
>>> link is way to slow to test this...
>>>
>>> Best Regards
>>> Sebastian
>>>
>>> >
>>> >
>>> > On Sun, Oct 19, 2014 at 10:51 AM, Ernesto Elias <
>>> ernestogelias@gmail.com> wrote:
>>> >> Hello everyone!
>>> >> I have a question about the wndr3800 routing limit. I went back to
>>> the older
>>> >> submissions to see if I can find what would be the answer for it. But
>>> in my
>>> >> search I haven't managed to find a definite answer. From what I seen
>>> about
>>> >> setting the limit it can do with SQM is 50, 60, or 80 mbit. I'm just
>>> >> wondering if anyone can shed some light for me here as I have verizon
>>> fios
>>> >> and my speeds are 50 dl/50 ul. Thank you guys very much!
>>> >>
>>> >> _______________________________________________
>>> >> Cerowrt-devel mailing list
>>> >> Cerowrt-devel@lists.bufferbloat.net
>>> >> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Dave Täht
>>> >
>>> > thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>>> > _______________________________________________
>>> > Cerowrt-devel mailing list
>>> > Cerowrt-devel@lists.bufferbloat.net
>>> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>>
[-- Attachment #2: Type: text/html, Size: 5124 bytes --]
next prev parent reply other threads:[~2014-10-19 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 17:51 Ernesto Elias
2014-10-19 18:24 ` Dave Taht
2014-10-19 18:48 ` Ernesto Elias
2014-10-19 18:51 ` Dave Taht
2014-10-19 19:16 ` Ernesto Elias
2014-10-19 19:55 ` Sebastian Moeller
2014-10-20 1:08 ` Ernesto Elias
2014-10-20 8:11 ` Sebastian Moeller
2014-10-21 2:30 ` Ernesto Elias
2014-10-21 8:23 ` Sebastian Moeller
2014-10-22 19:39 ` Ernesto Elias
2014-10-22 20:36 ` Sebastian Moeller
2014-10-23 22:03 ` Ernesto Elias
2014-10-24 11:38 ` Sebastian Moeller
2014-10-19 18:56 ` Sebastian Moeller
2014-10-19 19:22 ` Dave Taht
2014-10-19 19:33 ` Ernesto Elias
2014-10-19 19:41 ` Dave Taht [this message]
[not found] ` <CAA93jw6DFxoDaRVCoQn=zxbOjgQ-dA1bCZ1W=p9br25jWrRgkg@mail.gmail.com>
2014-10-19 22:44 ` Sebastian Moeller
2014-10-20 20:04 ` Dave Taht
2014-10-20 22:48 ` Dave Taht
2014-10-21 3:35 ` Aaron Wood
2014-10-21 7:43 ` Sebastian Moeller
2014-10-21 7:51 ` 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=CAA93jw6VvtLAMN-TwVdj+2SX9V7Xg8RN9B9LaB8SqPmUhQY+nA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ernestogelias@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