From: jb <justinbeech@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Brandon Applegate <brandon@burn.net>,
bloat <Bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports bufferbloat tests
Date: Wed, 6 Apr 2016 13:19:14 +1000 [thread overview]
Message-ID: <CAH3Ss96e-k4rvYwEt40a8qcLK7u1CwMrHpe5N7uwjszg3h3sCA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw409hG1VDJLJJaqSYY=ZArCH-p40aoeS=EkBpW_m5NhAA@mail.gmail.com>
I take your point regarding Quality
but both your examples in the post show A+ quality?
I'm thinking that packet loss significant enough to show as a "C" or
worse is mostly a bad situation
even if avoiding all packet loss - by using huge buffers - is
definitely a disaster..
On Wed, Apr 6, 2016 at 12:21 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Tue, Apr 5, 2016 at 6:33 PM, Brandon Applegate <brandon@burn.net> wrote:
>>
>>> On Apr 5, 2016, at 9:04 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> Does anyone know what the "quality" portion of dslreport's metric means?
>>
>> Basically - packet loss.
>>
>> https://www.dslreports.com/faq/17930
>
> Sigh. I ranted. I might rant harder.
>
> http://blog.cerowrt.org/post/bufferbloat_vs_quality/
>
>>
>> —
>> Quality Grades
>>
>> Quality refers to average detected packet loss / re-transmit percentages during download phase. The higher the packet loss / re-transmit percentage the more inefficient the connection is, and a very poor result may be indicative of congestion, inside wiring issues or other problems that need addressing.
>>
>> 1% or less - A+
>> 2.5% or less - A
>> 3% or less - B
>> 5% or less - C
>> 12% or less - D
>> over 12% - F
>> —
>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-04-06 3:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 1:04 Dave Taht
2016-04-06 1:33 ` Brandon Applegate
2016-04-06 2:21 ` Dave Taht
2016-04-06 3:19 ` jb [this message]
2016-04-06 15:30 ` Dave Taht
2016-04-06 16:08 ` Kelvin Edmison
2016-04-07 18:13 ` Livingood, Jason
2016-04-07 18:23 ` Livingood, Jason
2016-04-20 6:06 ` jb
2016-04-20 6:10 ` Dave Taht
2016-04-20 12:43 ` Jonathan Morton
2016-04-20 22:53 ` jb
2016-04-21 2:22 ` Jonathan Morton
2016-04-07 2:06 ` jb
2016-04-07 2:14 ` Jonathan Morton
2016-04-07 18:16 ` Livingood, Jason
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=CAH3Ss96e-k4rvYwEt40a8qcLK7u1CwMrHpe5N7uwjszg3h3sCA@mail.gmail.com \
--to=justinbeech@gmail.com \
--cc=Bloat@lists.bufferbloat.net \
--cc=brandon@burn.net \
--cc=dave.taht@gmail.com \
/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