From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 0E3643B2A2 for ; Wed, 12 Oct 2016 20:57:26 -0400 (EDT) Received: by mail-lf0-x22b.google.com with SMTP id b75so105142149lfg.3 for ; Wed, 12 Oct 2016 17:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nr1pvo4xZZ+M3dxwhIE73FiaiwWDdWu6eV0K5Qb3ctU=; b=ejm1Ch+6txhGR9R92iwiUL34kRwVQVehEIUtdconPZrctMHk/okecf9bhni2y30u6q ONTYI8gJOOTyMTPPAEcts6+2qufJHfCpgkczaK1xmwVmd+zSw47dozMhV40rdBJbbiYn Too6nYPUxhQI/cVsUmb5CsT/XoGtEHla9qRUS2Mz4oZJfae2xL5dzs2YmBlaigQ9NagD n6JSilPzOhSu7+lcby7rQoo20HXUh5IDptRb13lZSTOg91cKUmRBMkeVO3O4bVMb1PIt YmWw0xHU53mnIc2YDJeMvaciIoPafWVQFpb7bZOZR1/lMvf2dfTl7nqnpagjlyJ+8YQc CGOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nr1pvo4xZZ+M3dxwhIE73FiaiwWDdWu6eV0K5Qb3ctU=; b=OifUnvc7B7WmU89BmYpFCkMzbtb0i6MCHlR9g1ltf/rRWwtFZ+vd+RMNiL/vkz4DCw QUW6nKZr1jgNOXoc4EuPfoTJU0/vGxVtwBILR8U56N18yoo3DetuMFmLD5deZVx5AMlB cU8EvMK54Vozj7/4mMlmY5aP0Nuqxf3ghwvyBnvhV0ruqnGI0PZoDhLQYLSDZS1SblSm VMkQIjT6r+5hMxMn/RtTQ2cF2qt39tdCpZZtTLMewq6biX84/3WjUxFlRM4osSiV9VWB 9SVgp5jQAyLqNn9fBdnsq8NcLBEuiKuhxUDOAGveg+3uz/uuJGkyuihS+K5BQDe4A8Py XaFw== X-Gm-Message-State: AA6/9RnUfk7yOJhhy3qaGYG34L7T4iLOk5t6woqBuQ8LoFK6y+BSk3EN1CPRtNkq5yHLLE1sBjJr+TRU2xCGEw== X-Received: by 10.28.38.131 with SMTP id m125mr88198wmm.44.1476320244850; Wed, 12 Oct 2016 17:57:24 -0700 (PDT) MIME-Version: 1.0 Sender: justinbeech@gmail.com Received: by 10.28.207.134 with HTTP; Wed, 12 Oct 2016 17:57:24 -0700 (PDT) In-Reply-To: References: From: jb Date: Thu, 13 Oct 2016 11:57:24 +1100 X-Google-Sender-Auth: hB9lGq8g68wE1-k3qy4GI97qm0I Message-ID: To: Dave Taht Cc: bloat Content-Type: multipart/alternative; boundary=94eb2c03f04ec4e7b3053eb49727 Subject: Re: [Bloat] grading bloat better X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 00:57:26 -0000 --94eb2c03f04ec4e7b3053eb49727 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It is done under the trimmed mean method, that would be a "C" grade result. On Thu, Oct 13, 2016 at 11:46 AM, jb wrote: > Actually I think the concept I need is the trimmed mean. > throwing away the highest couple of values (lowest couple are not to be > thrown away because they can't be errant). > It isn't perfect but it would help. > > On Thu, Oct 13, 2016 at 11:39 AM, jb wrote: > >> A while ago I changed from mean to median with the reasoning being that >> one spike to a crazy level was not representative of bloat but instead >> representative of a network stall or other anomaly. Graphs that were nea= rly >> all good samples with one outlier were being unfairly graded poorly. >> >> But this example has the opposite issue - the median of this set of >> samples is the first half where everything is ok. Hence the good score. >> Using a mean would be correct for this sample. >> What should happen is to throw away a couple (max) outliers first, then >> do a mean to avoid punishing the results that come in as good but includ= e >> one errant measurement. >> >> thanks >> -Justin >> >> On Wed, Oct 12, 2016 at 11:16 PM, Dave Taht wrote: >> >>> This has major bloat happening at the end of the upload test. Which >>> worries me - here, at a gbit. >>> >>> http://www.dslreports.com/speedtest/5284047 >>> >>> -- >>> Dave T=C3=A4ht >>> Let's go make home routers and wifi faster! With better software! >>> http://blog.cerowrt.org >>> _______________________________________________ >>> Bloat mailing list >>> Bloat@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/bloat >>> >> >> > --94eb2c03f04ec4e7b3053eb49727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is done
under the trimmed mean method, that would b= e a "C" grade result.



On Thu, Oct 13, 201= 6 at 11:46 AM, jb <justin@dslr.net> wrote:
Actually I think the concept I need is the = trimmed mean.
throwing away the highest couple of values (lowest couple= are not to be thrown away because they can't be errant).
It = isn't perfect but it would help.

On T= hu, Oct 13, 2016 at 11:39 AM, jb <justin@dslr.net> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
A while ago I changed from m= ean to median with the reasoning being that one spike to a crazy level was = not representative of bloat but instead representative of a network stall o= r other anomaly. Graphs that were nearly all good samples with one outlier = were being unfairly graded poorly.

But this example has = the opposite issue - the median of this set of samples is the first half wh= ere everything is ok. Hence the good score. Using a mean would be correct f= or this sample.
What should happen is to throw away a couple (max= ) outliers first, then do a mean to avoid punishing the results that come i= n as good but include one errant measurement.

than= ks
-Justin

On Wed, Oct 12, 2016 at 11:16 PM, Dave Taht <dav= e.taht@gmail.com> wrote:
Th= is has major bloat happening at the end of the upload test. Which
worries me - here, at a gbit.

http://www.dslreports.com/speedtest/5284047

--
Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
ht= tp://blog.cerowrt.org
_______________________________________________
Bloat mailing list
Bloat@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat



--94eb2c03f04ec4e7b3053eb49727--