From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id BE1DF21F3E2 for ; Mon, 20 Apr 2015 07:51:15 -0700 (PDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id t3KEp6Bd013552; Mon, 20 Apr 2015 07:51:06 -0700 Date: Mon, 20 Apr 2015 07:51:06 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: jb In-Reply-To: Message-ID: References: <87wq18jmak.fsf@toke.dk> <87oamkjfhf.fsf@toke.dk> <87k2x8jcnw.fsf@toke.dk> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="===============2242108170878097270==" Cc: bloat@lists.bufferbloat.net 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: Mon, 20 Apr 2015 14:51:46 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --===============2242108170878097270== Content-Type: TEXT/Plain; format=flowed; charset=US-ASCII On Mon, 20 Apr 2015, jb wrote: > 2. The test does not do latency pinging on 3G and GPRS > because of a concern I had that with slower lines (a lot of 3G results are > less than half a megabit) the pings would make the speed measured > unreliable. And/or, a slow android phone would be being asked to do too > much. I'll do some tests with and without pinging on a 56kbit shaped line > and see if there is a difference. If there is not, I can enable it. remember that people can be testing from a laptop tethered to a phone. > 3. The graph of latency post-test is log X-axis at the moment > because one spike can render the whole graph almost useless with axis > scaling. What I might do is X-Axis breaking, and see if that looks ok. > Alternatively, a two panel graph, one with 0-200ms axis, the other in full > perspective. Or just live with the spike. Or scale to the 95% highest > number and let the other 5% crop. There are tool-tips after all to show the > actual numbers. I think that showing the spike is significant because that latency spike would impact the user. It's not false data. showing two graphs may be the way to go. I don't think showing the 95th percentile is right. Again it is throwing away significant datapoints. I think summarizing the number as an average (with error bands) for each category of the test would be useful. David Lang --===============2242108170878097270== Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: Content-Description: Content-Disposition: INLINE _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat --===============2242108170878097270==--