From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 9932F21F36B for ; Thu, 23 Apr 2015 14:45:02 -0700 (PDT) Received: by qkx62 with SMTP id 62so19582267qkx.0 for ; Thu, 23 Apr 2015 14:45:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=FxxHVq4AgqFN0Is81bKcZuY/kruU6c8W9c3YrzqWp/w=; b=TqynxEZo8OMIyW88hO6rMb4TdYsUeC2M7s0SOgc7BK5CjXwvWyU6Bb2HpUERM4FOXy elTPaoRJC+Ig63UWRfrbS0zvAoCwOmCpAMXiq5unlOH/1hTBxfknuTt4N2GeGZOQecOt gmrEfbsFjOo92kon1g6sGsixy/rJmxGFgJGEmq6wg3IVRNNGfFrpOQd3rfHVAHG0Krrw 8b2B0CVg05DUCIKPJ5QBZcCasSmy9h2+daS5fYu3RqXcjvwIvKFMzY+MTbOnWKVu97cZ 38LXadFHc7KLueFiwaCEaFsQ/w4iRzRGm+RrnOjEGZ04VDsFrjZbl87lS93d2ieOnOxj BA3w== X-Received: by 10.55.53.72 with SMTP id c69mr9680083qka.67.1429825500973; Thu, 23 Apr 2015 14:45:00 -0700 (PDT) Received: from richs-mbp-11889.home.lan (d-ptld-bng1-71-161-114-95.ngn.east.myfairpoint.net. [71.161.114.95]) by mx.google.com with ESMTPSA id 8sm6826493qhs.5.2015.04.23.14.44.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Apr 2015 14:45:00 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Rich Brown In-Reply-To: Date: Thu, 23 Apr 2015 17:44:57 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <0D391BB1-9CA5-4DAF-8FD6-6628AB09C1C5@gmail.com> References: <87wq18jmak.fsf@toke.dk> <87oamkjfhf.fsf@toke.dk> <87k2x8jcnw.fsf@toke.dk> To: bloat X-Mailer: Apple Mail (2.1878.6) Subject: Re: [Bloat] DSLReports Speed Test has latency measurement built-in X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2015 21:45:30 -0000 Hi Justin, The newest Speed Test is great! It is more convincing than I even = thought it would be. These comments are focused on the "theater" of the = measurements, so that they are unambiguous, and that people can figure = out what's happening I posted a video to Youtube at: http://youtu.be/EMkhKrXbjxQ to = illustrate my points. NB: I turned fq_codel off for this demo, so that = the results would be more extreme. 1) It would be great to label the gauge as "Latency (msec)" I love the = term "bufferbloat" as much as the next guy, but the Speed Test page = should call the measurement what it really is. (The help page can = explain that the latency is almost certainly caused by bufferbloat, but = that should be the place it's mentioned.) 2) I can't explain why the latency gauge starts at 1-3 msec. I am = guessing that it's showing incremental latency above the nominal value = measured during the initial setup. I recommend that the gauge always = show actual latency. Thus the gauge could start at 45 msec (0:11 in the = video) then change during the measurements. 3) I was a bit confused by the behavior of the gauge before/after the = test. I'd like it to change only when when something else is moving in = the window. Here are some suggestions for what would make it clearer: - The gauge should not change until the graph starts moving. I = found it confusing to see the latency jump up at 0:13 just before the = blue download chart started, or at 0:28 before the upload chart started = at 0:31. - Between the download and upload tests, the gauge should drop = back to the nominal measured values. I think it does. - After the test, the gauge should also drop back to the nominal = measured value. It seems stuck at 4928 msec (0:55). 4) I like the way the latency gauge changes color during the test. It's = OK for it to use the color to indicate an "opinion". Are you happy with = the thresholds for yellow & red colors? 5) The gauge makes it appear that moderate latency - 765 msec (0:29) - = is the same as when the value goes to 1768 msec (0:31), and also when it = goes to 4,447 msec (0:35), etc. It might make more sense to have the = chart's full-scale at something like 10 seconds during the test. The = scale could be logarithmic, so that "normal" values occupy up to a third = or half of scale, and bad values get pretty close to the top end. = Horrible latency - greater than 10 sec, say - should peg the indicator = at full scale. 6) On the Results page (1:20), I like the red background behind the = latency values. I don't understand why the grey bars at the right end of = the chart are so high. Is the latency still decreasing as the queue = drains? Perhaps the ping tests should run longer until it gets closer to = the nominal value. This is such a great tool. Thanks! Rich=