Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] archer c7 v2, policing, hostapd, test openwrt build
Date: Mon, 23 Mar 2015 17:05:21 -0700	[thread overview]
Message-ID: <CAA93jw7qEMD8pk3dRMxKuJo8fs9noBCxJ--NwmcgxF0jf7SVOA@mail.gmail.com> (raw)
In-Reply-To: <8AC58249-8199-405B-997A-E8F7285A34FB@gmx.de>

this is with cero or last weekend's build?

On Mon, Mar 23, 2015 at 5:00 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Jonathan, hi List,
>
>
> So I got around to a bit of rrul testing of the dual egress idea to asses the cost of IFB, but the results are complicated (so most likely I screwed up). On an wndr3700v2 on a 100Mbps/40Mbps link I get the following (excuse the two images either the plot is intelligble or the legend...):
>
>
>
> Only in case of shaping the total bandwidth to the ~70Mbps this router can barely do can I see an effect of the dual egress instead of the IFB based ingress shaper. So column 7 (ipv4) and column 8 (ipv6) are larger than columns 9 (ipv4) and 10 (ipv6) showing that dual egress instead of egress and ingress effective upload increases by < 10 Mbps (while download and latency stay unaffected). That is not bad, but also does not look like the IFB is the cost driver in sqm-scripts, or does it? Also as a corollary of the data I would say, my old interpretation that we hit a limit at ~70Mbps combined traffic might not be correct in that ingress and egress might carry slightly different costs, but then thins difference is not going to make a wndr punch way above its weight…
>
> Best Regards
>         Sebastian
>
>
>
>
> On Mar 23, 2015, at 17:09 , Sebastian Moeller <moeller0@gmx.de> wrote:
>
>> Hi Jonathan,
>>
>> On Mar 23, 2015, at 14:43 , Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>>
>>>> On 23 Mar, 2015, at 08:09, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>>
>>>> It obviously degrade local performance of se00 and hence be not a true solution unless one is happy to fully dedicate a box as shaper ;)
>>>
>>> Dedicating a box as a router/shaper isn’t so much of a problem, but shaping traffic between wired and wireless - and sharing the incoming WAN bandwidth between them, too - is.  outer
>>
>>       Exactly the sentiment I had, but less terse and actually understandable ;)
>>
>>> It’s a valid test, though, for this particular purpose.
>>
>>       Once I get around to test it, I should b able to share some numbers…
>>
>> Best Regards
>>       Sebastian
>>
>>>
>>> - Jonathan Morton
>>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

  reply	other threads:[~2015-03-24  0:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  0:24 Dave Taht
2015-03-23  0:31 ` Jonathan Morton
2015-03-23  1:10 ` Jonathan Morton
2015-03-23  1:18   ` Dave Taht
2015-03-23  1:34 ` Jonathan Morton
2015-03-23  1:45   ` David Lang
2015-03-23  2:00     ` Dave Taht
2015-03-23  2:10     ` Jonathan Morton
2015-03-23  2:15       ` Dave Taht
2015-03-23  2:18         ` Dave Taht
2015-03-23  6:09       ` Sebastian Moeller
2015-03-23 13:43         ` Jonathan Morton
2015-03-23 16:09           ` Sebastian Moeller
2015-03-24  0:00             ` Sebastian Moeller
2015-03-24  0:05               ` Dave Taht [this message]
2015-03-24  0:07                 ` Sebastian Moeller
2015-03-24  3:16               ` Jonathan Morton
2015-03-24  7:47                 ` Sebastian Moeller
2015-03-24  8:13                   ` Jonathan Morton
2015-03-24  8:46                     ` Sebastian Moeller
2015-03-29  1:14                     ` Sebastian Moeller
2015-03-29  6:17                       ` Jonathan Morton
2015-03-29 11:16                         ` Sebastian Moeller
2015-03-29 12:48                           ` Jonathan Morton
2015-03-29 14:16                             ` Sebastian Moeller
2015-03-29 15:13                               ` Jonathan Morton
2015-03-23 17:08       ` David Lang
2015-03-23 16:17 ` Sebastian Moeller
2015-03-23 16:27   ` Dave Taht
2015-03-23 17:07     ` David Lang
2015-03-23 18:16       ` Jonathan Morton

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=CAA93jw7qEMD8pk3dRMxKuJo8fs9noBCxJ--NwmcgxF0jf7SVOA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=moeller0@gmx.de \
    /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