From: Sebastian Moeller <moeller0@gmx.de>
To: "David P. Reed" <dpreed@reed.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Problems testing sqm
Date: Sat, 24 Oct 2015 10:07:18 +0200 [thread overview]
Message-ID: <FCA7B9A7-1B9F-4ECF-9BA7-38B6C24DDF25@gmx.de> (raw)
In-Reply-To: <c41ecd1b-7e4d-4bb6-822d-e20b1f5e1c1b@reed.com>
Hi David,
On Oct 24, 2015, at 00:53 , David P. Reed <dpreed@reed.com> wrote:
> In particular, the DUT should probably have no more than 2 packets of outbound queueing given the very small RTT. 2xRTT is the most buffering you want in the loop.
Let’s not haggle about the precise amount of queueing we deem acceptable, as long as we all agree that >= 2 seconds is simply not acceptable ;) (the default sqm will approximately limit the latency under load increase (LULI) to roughly twice the target or typically 10 ms; note that this LULI only applies to unrelated flows). The exact number of queued packets seems to correlate with the beefiness of the DUT, the beefier the fewer packets should work, wimpier devices might need to batch some processing up, resulting in higher LULI…
Best Regards
Sebastian
>
> On Oct 23, 2015, Richard Smith <smithbone@gmail.com> wrote:
> On 10/23/2015 02:41 PM, Michael Richardson wrote:
> Richard Smith <smithbone@gmail.com> wrote:
> My test setup:
>
> Laptop<--1000BaseT-->DUT<--1000baseT-->Server
>
> So, given that the DUT is the only real constraint in the network, what
> do you expect to see from this setup?
>
> Given that the probably DUT can't forward at Gb/s, and it certainly can't
> shape anything, it's gonna drop packets, and it's probably gonna drop them in
> Rx, having overrun the Rx-queue (so tail-drop). If there is too much ram
> (bufferbloated), then you'll see different results...
>
> Setting ingress/egress to 10Mbit/s I expected to see the speed
> measurements bounce around those limits with the ping times staying in
> the low double digits of ms. What I saw however, was the data rates
> going well past 10Mbit limit and pings up to 2000 ms.
>
> This is what I've seen in prior rrul testing using a the 50/10 cable
> link at our office and my 25(ish)/6 link at my apartment and a well
> connected server on the net. That however was using QoS and not SQM.
>
> Its that a reasonable expectation?
>
> -- Sent with K-@ Mail - the evolution of emailing. _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-10-24 8:07 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:10 Richard Smith
2015-10-23 16:13 ` Dave Taht
2015-10-23 16:21 ` Rich Brown
2015-10-23 16:45 ` Richard Smith
2015-10-23 16:43 ` Richard Smith
2015-10-23 17:42 ` Sebastian Moeller
2015-10-23 17:15 ` David Lang
2015-10-23 17:02 ` Alan Jenkins
2015-10-23 17:30 ` Richard Smith
2015-10-23 17:50 ` Sebastian Moeller
2015-10-23 17:45 ` Sebastian Moeller
2015-10-23 17:22 ` Aaron Wood
2015-10-23 17:47 ` Sebastian Moeller
2015-10-23 17:48 ` Richard Smith
2015-10-23 17:57 ` David Lang
2015-10-23 19:08 ` Sebastian Moeller
2015-10-23 17:38 ` Sebastian Moeller
2015-10-23 18:05 ` Richard Smith
2015-10-23 18:41 ` Michael Richardson
2015-10-23 20:18 ` Richard Smith
2015-10-23 22:48 ` David P. Reed
2015-10-24 7:59 ` Sebastian Moeller
2015-10-23 22:51 ` Aaron Wood
2015-10-23 22:53 ` David P. Reed
2015-10-24 8:07 ` Sebastian Moeller [this message]
2015-10-24 16:34 ` David P. Reed
2015-10-24 16:52 ` Jonathan Morton
2015-10-24 18:58 ` David P. Reed
2015-10-25 23:21 ` David Lang
2015-10-26 9:53 ` Jonathan Morton
2015-10-24 17:24 ` Sebastian Moeller
2015-10-24 17:30 ` Aaron Wood
2015-10-24 10:20 ` Dave Taht
2015-10-24 17:21 ` Sebastian Moeller
2015-10-25 15:10 ` Richard Smith
2015-10-25 16:07 ` [Cerowrt-devel] Problems testing sqm (solved) Richard Smith
2015-10-25 17:36 ` Rich Brown
2015-10-25 20:02 ` Richard Smith
2015-10-25 20:33 ` Sebastian Moeller
2015-10-25 20:44 ` Richard Smith
2015-10-26 11:17 ` Toke Høiland-Jørgensen
2015-10-26 12:35 ` Richard Smith
2015-10-26 11:50 ` Dave Taht
2015-10-26 12:27 ` Richard Smith
2015-10-26 13:41 ` Sebastian Moeller
2015-10-26 13:48 ` Dave Taht
2015-10-26 18:15 ` David Lang
2015-10-26 18:26 ` Sebastian Moeller
2015-10-26 18:31 ` David Lang
2015-10-26 21:01 ` Richard Smith
2015-10-26 22:23 ` Richard Smith
2015-10-26 13:50 ` [Cerowrt-devel] ***UNCHECKED*** " Toke Høiland-Jørgensen
2015-10-26 14:30 ` Sebastian Moeller
2015-10-26 21:54 ` Richard Smith
2015-10-26 22:04 ` Richard Smith
2015-10-25 20:07 ` [Cerowrt-devel] " Sebastian Moeller
2015-10-25 21:50 ` Jonathan Morton
2015-10-25 22:44 ` Richard 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=FCA7B9A7-1B9F-4ECF-9BA7-38B6C24DDF25@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.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