From: "Török Edwin" <edwin@etorok.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-9 released
Date: Tue, 18 Mar 2014 18:49:27 +0200 [thread overview]
Message-ID: <53287917.5020503@etorok.net> (raw)
In-Reply-To: <CAA93jw442My8sUH=GCS+=A2Yqi2mPEY4_eajJy+UwZkmKWszdA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]
On 03/18/2014 05:35 PM, Dave Taht wrote:
> On Tue, Mar 18, 2014 at 11:22 AM, Török Edwin <edwin@etorok.net> wrote:
>> Should I also run a rrul46/rrul46compete test?
>
> If you can test ipv6 too, that would be great.
Attached IPv6 results.
>
> At 8ms of induced extra latency without SQM there doesn't seem to be
> much point in running it on your platform. It does look like you are tail
> dropping...
>
> A thought would be to leave it
> off and try running your link at 100Mbit rather than gige.
>
> # ethtool -s ge00 advertise 0x008
Well ge00 already runs at 100Mbit, because ISP plugged me into a 100Mbit port on the switch:
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
They would plug me into a 1Gbit port only if I pay for 1Gbps connectivity, which is in fact only 7 EUR/month more, but its not available in my area yet :)
>
> and see if fq_codel alone can break up bursts better.
>
> I note that linux 3.14 TCP is now so highly debloated that it is really hard to
> compare the results we get with it with any TCP before it - the TSO offload
> fixes, tcp small queues, etc, have really shortened and made more accurate
> the control loops.
>
> second note is that the wndr can only forward packets at about 330Mbit
> without firewall rules. Add in the firewall rules and you are looking at
> sub 120mbit forwarding performance.
Good to know, not much point in purchasing 1Gbit connectivity from my ISP unless I also replace my router.
>
> I am jealous of your link. :)
Best regards,
--Edwin
[-- Attachment #2: rrul46_compete_sqm_off.png --]
[-- Type: image/png, Size: 262670 bytes --]
[-- Attachment #3: rrul46_compete_sqm_on.png --]
[-- Type: image/png, Size: 276876 bytes --]
[-- Attachment #4: rrul46_sqm_on.png --]
[-- Type: image/png, Size: 211120 bytes --]
[-- Attachment #5: rrul46_sqm_off.png --]
[-- Type: image/png, Size: 225381 bytes --]
next prev parent reply other threads:[~2014-03-18 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 19:58 Dave Taht
2014-03-16 21:27 ` Valdis.Kletnieks
2014-03-16 21:45 ` Dave Taht
2014-03-17 0:03 ` Toke Høiland-Jørgensen
2014-03-17 0:42 ` Valdis.Kletnieks
2014-03-17 0:54 ` Dave Taht
2014-03-17 12:20 ` Michael Richardson
2014-03-17 13:40 ` Dave Taht
2014-03-17 14:30 ` Toke Høiland-Jørgensen
2014-03-17 14:39 ` Toke Høiland-Jørgensen
2014-03-17 14:55 ` Dave Taht
2014-03-17 14:55 ` Michael Richardson
2014-03-17 15:18 ` Dave Taht
2014-03-18 10:00 ` Török Edwin
2014-03-18 12:12 ` Sebastian Moeller
2014-03-18 14:21 ` Dave Taht
2014-03-18 15:22 ` Török Edwin
2014-03-18 15:35 ` Dave Taht
2014-03-18 16:49 ` Török Edwin [this message]
2014-03-18 17:03 ` Dave Taht
2014-03-18 17:06 ` Valdis.Kletnieks
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=53287917.5020503@etorok.net \
--to=edwin@etorok.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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