From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 6503B3B2A2 for ; Wed, 12 Oct 2016 20:46:56 -0400 (EDT) Received: by mail-lf0-x236.google.com with SMTP id l131so70123034lfl.2 for ; Wed, 12 Oct 2016 17:46:56 -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=r/PbcdpmoMhLSxbDEidCkOFi/72R/+NCK6B2aGzWrMY=; b=ZI0fE0i33lzQ/Ae2hKFZsE+9t1VaDCMESez5GJNrvCqdUyLATiCEVdJhqBLPICfkau WohyCasBFHNokVReOgC3dYZOPgtBMgCTIvanNZyh4okb71vLlhEqhuATN6E5lFxZE1KE Vozxx2ECA20o8/xNxO6NN3VU+IfhmYwpZCoE2ZMgLsjor7sPWHP2wGzKxd+Zw059MPOG sVO7Td4bbUaDwmUeq9sG2Edl3DT91CWWdscoTJoUwCevbH98g16ooNAfnjCQqdVruddB MXXLuwVkoxQFB0x4CrFQNW0juVMJzuFJscKgSKHoYbYBOTzFHY1cr6CjsuwEWpzTvvyl C+8Q== 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=r/PbcdpmoMhLSxbDEidCkOFi/72R/+NCK6B2aGzWrMY=; b=K+EhKe2cOHxewzVQw9+QGguwx6UQ88XZKl+bsKTfAgZo+JQdjKIEFfCfVPCA8R4hRt SUylsyNChuLmMy29bk98FcVaz7CrIzGtMtzpEZ8aLk1V9+AdeqnV866nxrVeDpKK1MfD Gulx1GHNzMNGmN+PGonjW7FC/n9NswWIRQWkEdDpaqkiOKE2J239HHl9fptqfJd+YgVk 86wKdUl00U/oSrra6UcOEcAVefnB/YB8I/aJUX0rmZQRlOShWIi+Lh/9nwJJxZ4F6RWw YyMmZorLR31tbtOHNpzfyGWMWfv4u5MUpXkdEcl4GJJ1WJ5hjosTaDvlJbU+4uuwLpV7 l+NA== X-Gm-Message-State: AA6/9RnmIpLc2ZrxlVYIB5/kH6XF028Bf74TEfWn4D5wOesiGJejvVAvwAHsHc4p87xP7CzIU1Fd83uaiYcNwg== X-Received: by 10.28.140.129 with SMTP id o123mr70654wmd.51.1476319615157; Wed, 12 Oct 2016 17:46:55 -0700 (PDT) MIME-Version: 1.0 Sender: justinbeech@gmail.com Received: by 10.28.207.134 with HTTP; Wed, 12 Oct 2016 17:46:54 -0700 (PDT) In-Reply-To: References: From: jb Date: Thu, 13 Oct 2016 11:46:54 +1100 X-Google-Sender-Auth: YmyX8HQBlGPrPycsGb247312Hgc Message-ID: To: Dave Taht Cc: bloat Content-Type: multipart/alternative; boundary=001a11497b703c8ce2053eb47257 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:46:56 -0000 --001a11497b703c8ce2053eb47257 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 near= ly > 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 d= o > a mean to avoid punishing the results that come in as good but include on= e > 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 >> > > --001a11497b703c8ce2053eb47257 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 perfe= ct but it would help.

On Thu, Oct 13, 2016 at 11:39 AM, jb <= ;justin@dslr.net&g= t; 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 nearly all good samp= les 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 me= an would be correct for this sample.
What should happen is to thr= ow away a couple (max) outliers first, then do a mean to avoid punishing th= e results that come in as good but include one errant measurement.

thanks
-Justin
=

On Wed, Oct 12, 2016 at 11:16 PM, Dave Taht <dave.taht@gmail.com&g= t; wrote:
This has major bloat hap= pening 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


--001a11497b703c8ce2053eb47257--