From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (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 9CC3721F295 for ; Thu, 21 May 2015 06:45:39 -0700 (PDT) Received: by qgew3 with SMTP id w3so39726187qge.2 for ; Thu, 21 May 2015 06:45:38 -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:cc :content-transfer-encoding:message-id:references:to; bh=WwNSsQbyBEsmpD7tA13ZAAKddMMTu8SFkwq3x4IB1v8=; b=yd155y85xm2KkgHFAA4Y3HsWaolMtdB/BsbwzpOHb3YPef/8G+yw53GbRw/HAFeuIm +bSPl7sKnAGfr3krOwCOWAUN9xfbj/APoqwJ6BhhZ1OOFvd86/qRam7WlkBTN9R1SznW 7zx0cIfdMcEAU7rMCDu4UPoHj7W4Utx4H2NoF7BCeL7C9NdzfEmuIindm4kloZqGJvxX fCebOPDlwc1VmQtfxBYNTNhBNYhnG/4S9h22eWCJWqRBzgetKpqog/3P75OuimwTxaRe t6kVP2AlvUoxtGq5V4h9ytbOw1/GbkwFEBKBsMbhfGhK3hfZbEgVG5oUbzv73HnHKHXu tiuA== X-Received: by 10.55.52.4 with SMTP id b4mr6066063qka.37.1432215938575; Thu, 21 May 2015 06:45:38 -0700 (PDT) Received: from richs-mbp-12926.lan ([64.222.210.94]) by mx.google.com with ESMTPSA id b141sm13358283qka.11.2015.05.21.06.45.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 May 2015 06:45:37 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Rich Brown In-Reply-To: Date: Thu, 21 May 2015 09:45:35 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <58264BE0-CDBE-4739-B03D-4BAA20B13997@gmail.com> References: To: Dave Taht X-Mailer: Apple Mail (2.1878.6) Cc: bloat Subject: Re: [Bloat] dslreports mockup 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, 21 May 2015 13:46:08 -0000 That is interesting. I'm trying to think how the latency charts could be = misconstrued, since a Y-axis on the right isn't the norm - I don't think = it's hard to understand, but just different.=20 The display as-is clearly shows that the download is badly bloated, but = the upload is fine. That's the important message for most people at = home. But as a researcher, you want to understand the details of the = upload. So having different scales would help you see better into the = problem.=20 * If the download and upload values are substantially similar, the left = and right Y-axis scales should be the same, so there wouldn't be = confusion * If the values are substantially different (as in this screen shot), = the pink and yellow backgrounds (on the left) and the lack of them on = the right would provide a solid cue that there is something different = going on between the two charts. * On the other hand, the report already shows different Y-axis values = for the down/upload speeds, so the latency charts could mimic the = speeds... Other thoughts? Rich On May 20, 2015, at 12:46 PM, Dave Taht wrote: > I wanted to be able to have separated charts for up and down on > different scales, so I took apart what exists today in gimp and got > this: >=20 > http://snapon.lab.bufferbloat.net/~d/dslreportsmockup.png >=20 > I guess it is partially because I am getting a C on the download at > this speed, and no A+ on the upload, and I would at least like to get > a gold star from teacher for effort. :/ >=20 > I dunno how to fix the download short of getting rid of several > seconds of inherent buffering in their CMTS. There must be a simple > way to do that?? >=20 > --=20 > Dave T=E4ht > Open Networking needs **Open Source Hardware** >=20 > https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67 > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat