Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Aaron Wood <woody77@gmail.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] ingress rate limiting falling short
Date: Wed, 03 Jun 2015 17:58:03 +0200	[thread overview]
Message-ID: <F39AE226-D1AF-447A-9285-E0CED9692338@gmx.de> (raw)
In-Reply-To: <CALQXh-OjiUaStSrVAOcRodA8eGCL2eExNO76Ncu-7i3JJPRPPw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]

Hi Aaron,

about the 5% loss with the wndr, please remember that the shaper works typically on raw Ethernet rates, while flent reports TCP good put I believe. So roughly 2 to 6 percent difference can be explained with a combination of the following overheads: PTM/ATM, ethernet, VLAN(s), PPPoE, IPv4/IPv6, TCP, potential TCP options like timestamps... Now flent might report actual tcp-rates and I am out to lunch, but I have a hard time reconciling  how flent/netperf, can actually learn about all the additional overhead... As far as I can tell all netperf sees is the payload it sends and the payload it receives...
Tl;dr: Overhead unknown to flent effortlessly explains why the TCP good put as reported by flent falls short of the shaped rate as that rate contains all overheads.


Best Regards
        Sebastian

On June 3, 2015 7:45:47 AM GMT+02:00, Aaron Wood <woody77@gmail.com> wrote:
>I wrote this up on my blog, where I can intersperse text and graphs a
>bit
>better:
>
>http://burntchrome.blogspot.com/2015/06/htb-rate-limiting-not-quite-lining-up.html
>
>Basically, I ran a series of tcp_download tests, using increasing
>ingress
>rates with sqm_scripts, and then used flent's box-plots to put the
>results
>into a combined image for comparing.
>
>On the 3800, it never meets the rate, but it's only off by maybe 5%. 
>But
>on my new WRT1900AC, it's wildly off, even over the same performance
>range
>(I tested it from 80-220Mbps rates in 20Mbps jumps, and saw from
>40-150Mbps.
>
>I have no idea where to start looking for the cause.  But for now, I'm
>just
>setting my ingress rate MUCH higher than I should, because it's working
>out
>to the right value as a result.
>
>-Aaron
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2607 bytes --]

  parent reply	other threads:[~2015-06-03 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  5:45 Aaron Wood
2015-06-03  6:00 ` Dave Taht
2015-06-03 15:53 ` Jonathan Morton
2015-06-03 15:58 ` Sebastian Moeller [this message]
2015-06-03 16:25 ` Jonathan Morton
2015-06-03 17:49 ` Sebastian Moeller
2015-06-03 22:16   ` Aaron Wood
2015-06-03 22:27     ` Dave Taht
2015-06-03 22:34       ` Dave Taht
2015-06-03 22:43       ` Aaron Wood

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=F39AE226-D1AF-447A-9285-E0CED9692338@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@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