<html><head></head><body>Not trying to haggle. Just pointing out that this test configuration has a very short RTT. maybe too short for our SQM to adjust to.<br clear="none"><br clear="none"><div class="gmail_quote">On Oct 24, 2015, Sebastian Moeller <moeller0@gmx.de> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k10mail">Hi David,<br clear="none"><br clear="none">On Oct 24, 2015, at 00:53 , David P. Reed <dpreed@reed.com> wrote:<br clear="none"><br clear="none"></pre><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">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.</blockquote><br clear="none"> 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…<br clear="none"><br clear="none">Best Regards<br clear="none"> Sebastian<br clear="none"><br clear="none"><br clear="none"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Oct 23, 2015, Richard Smith <smithbone@gmail.com> wrote:<br clear="none">On 10/23/2015 02:41 PM, Michael Richardson wrote:<br clear="none">Richard Smith <smithbone@gmail.com> wrote:<br clear="none">My test setup:<br clear="none"><br clear="none">Laptop<--1000BaseT-->DUT<--1000baseT-->Server<br clear="none"><br clear="none">So, given that the DUT is the only real constraint in the network, what<br clear="none">do you expect to see from this setup?<br clear="none"><br clear="none">Given that the probably DUT can't forward at Gb/s, and it certainly can't<br clear="none">shape anything, it's gonna drop packets, and it's probably gonna drop them in<br clear="none">Rx, having overrun the Rx-queue (so tail-drop). If there is too much ram<br clear="none">(bufferbloated), then you'll see different results...<br clear="none"><br clear="none">Setting ingress/egress to 10Mbit/s I expected to see the speed <br clear="none">measurements bounce around those limits with the ping times staying in <br clear="none">the low double digits of ms. What I saw however, was the data rates <br clear="none">going well past 10Mbit limit and pings up to 2000 ms.<br clear="none"><br clear="none">This is what I've seen in prior rrul testing using a the 50/10 cable <br clear="none">link at our office and my 25(ish)/6 link at my apartment and a well <br clear="none">connected server on the net. That however was using QoS and not SQM.<br clear="none"><br clear="none">Its that a reasonable expectation?<br clear="none"><br clear="none">-- Sent with K-@ Mail - the evolution of emailing.<hr><br clear="none">Cerowrt-devel mailing list<br clear="none">Cerowrt-devel@lists.bufferbloat.net<br clear="none"><a shape="rect" href="https://lists.bufferbloat.net/listinfo/cerowrt-devel">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a></blockquote><br clear="none"></blockquote></div><br clear="none">-- Sent with <b><a shape="rect" href="https://play.google.com/store/apps/details?id=com.onegravity.k10.pro2">K-@ Mail</a></b> - the evolution of emailing.</body></html>