From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: jb <justin@dslr.net>, Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports redux
Date: Tue, 3 Jan 2017 14:42:50 +0000 [thread overview]
Message-ID: <be5bb3a668714fd38a0b7d0568d980a8@PACDCEX43.cable.comcast.com> (raw)
In-Reply-To: <CAH3Ss976d7x+yjefK2ywftamS8gtNjJdyDtp2ykJDdQ9eB-n9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Is it correct to assume that the bufferbloat grade is based off of the difference between the idle latency and the upload / download latencies, and not some absolute value ranges of milliseconds?
Regards,
Carl Klatsky
From: Bloat [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of jb
Sent: Sunday, December 18, 2016 8:07 PM
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports redux
It gets that grade because the Idle latency is so awful there is really little difference between idle latency and other latency measurements..
They clearly have some issues with their connection, PC or browser, with that kind of latency over cable. So the buffer bloat reading (or giving any grades for anything) are kind of meaningless.
On Sun, Dec 18, 2016 at 7:35 AM, Dave Taht <dave.taht@gmail.com<mailto:dave.taht@gmail.com>> wrote:
This one gets an a+, ironically.
http://www.dslreports.com/speedtest/7261612
I'd like a "question this result" button, or some other way to kibitz.......
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
[-- Attachment #2: Type: text/html, Size: 4646 bytes --]
prev parent reply other threads:[~2017-01-03 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 20:35 Dave Taht
2016-12-17 20:55 ` Steinar H. Gunderson
2016-12-17 21:07 ` Jonathan Morton
2016-12-17 22:51 ` Steinar H. Gunderson
2016-12-19 1:06 ` jb
2017-01-03 14:42 ` Klatsky, Carl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be5bb3a668714fd38a0b7d0568d980a8@PACDCEX43.cable.comcast.com \
--to=carl_klatsky@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=justin@dslr.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox