From: jb <justin@dslr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] extremely good dslreports result for bufferbloat on free.fr
Date: Thu, 30 Apr 2015 14:33:56 +1000 [thread overview]
Message-ID: <CAH3Ss96JzO5mYyxFza9G6rKNOkT1OQxw+M_g32faLnuFxpFoJg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6gBTa2qPdV2DB8MivWjkDKpnXa_D8C6UzP_cC0Pv7hTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3688 bytes --]
yes it did get no rating, I don't generate ratings unless everything looks
"right",
meaning a decent number of down idle and up pings.
http://www.dslreports.com/speedtest/377563
There are only 6 latency samples during download, even though the download
phase started at the 12 second mark and continued until the 23 second mark,
(meaning 11 seconds).
The latency pings that happened during the download got held up to the
extent
that they came in and were counted as "idle" ones. I'll have to ponder on
this,
I think my pings need to be labelled by origin (what we were doing when they
were sent) not classified as they return.
if it did get a rating it would be an "D" or "F"..
On Thu, Apr 30, 2015 at 2:23 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Heh. Anything above a 250ms gets a F from me. But I strongly approve
> of simplification to a set of grades.
>
> http://www.dslreports.com/speedtest/378980 F, for sure.
>
> Secondly, we tend to regard bufferbloat as one word not two.
>
> This result got no rating. http://www.dslreports.com/speedtest/377563
>
> On Wed, Apr 29, 2015 at 9:07 PM, jb <justinbeech@gmail.com> wrote:
> > I've added the discussed "bloat rating".
> >
> > It takes the idle period before download uses the lowest latency as a
> > baseline.
> > then it takes the median download and median of upload+trailing idle
> time,
> > and
> > subtracts to get the latency increase, then converts to a grade.
> >
> > Based on a very few results I've looked at the Grade seems reasonable.
> I've
> > added
> > a link below the grade for the WTF is this moment a lot of people will
> have,
> > which
> > takes them to a short FAQ entry, and then a link to bufferbloat.net ..
> >
> >
> > On Thu, Apr 30, 2015 at 4:32 AM, Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> On Wed, Apr 29, 2015 at 9:32 AM, Juliusz Chroboczek
> >> <jch@pps.univ-paris-diderot.fr> wrote:
> >> > Free.fr (Proxad) is certainly much better than other ISPs -- they've
> >> > been
> >> > the first to give sort-of-native (6rd) IPv6 to the masses. However,
> >> > there's one thing that annoys me -- they have two distinct CPEs, the
> >> > classic FreeBox (which I have) and the FreeBox Revolution (which is
> >> > slightly less cheap, and takes more physical space -- a big deal if
> you
> >> > live in Paris). The classic FreeBox needs some love from the firmware
> >> > developers, and I'd be curious to know whether your results apply
> >> > equally
> >> > to both boxen.
> >>
> >> All ya gotta do is run the new dslreports and/or rrul test(s) on your
> >> own older box, and post. ;)
> >>
> >> My understanding was that the old freebox was too weak to run anything
> >> but SFQ, but it did run that on the outbound.
> >>
> >> >
> >> > (The thing that most pisses me off with the classic FreeBox is that it
> >> > doesn't allow IPv6 subnetting -- unless you order the FreeBox
> >> > Revolution,
> >> > you're condemned to the purgatory of ND-proxying. Grr.)
> >>
> >> As tiny as the mods now are to support more extensive ipv6 in openwrt,
> >> that certainly was not the case in 2012.
> >>
> >> >
> >> > -- Juliusz
> >>
> >>
> >>
> >> --
> >> Dave Täht
> >> Open Networking needs **Open Source Hardware**
> >>
> >> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >
> >
>
>
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
>
[-- Attachment #2: Type: text/html, Size: 5504 bytes --]
next prev parent reply other threads:[~2015-04-30 4:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:48 Dave Taht
2015-04-28 23:33 ` jb
2015-04-28 23:44 ` David Lang
2015-04-29 1:39 ` Jonathan Morton
2015-04-29 2:01 ` Dave Taht
2015-04-29 2:49 ` jb
2015-04-29 16:32 ` Juliusz Chroboczek
2015-04-29 18:32 ` Dave Taht
[not found] ` <CAH3Ss96FnwgK8qxdV-n46GLe2FSsRRa7zD1M_Wmq91o=+-7qdQ@mail.gmail.com>
2015-04-30 4:23 ` Dave Taht
2015-04-30 4:33 ` jb [this message]
2015-04-30 4:43 ` Dave Taht
2015-04-30 4:55 ` Dave Taht
2015-04-30 5:23 ` Dave Taht
2015-04-30 5:49 ` jb
2015-04-30 16:36 ` Dave Taht
2015-05-01 0:48 ` Rich Brown
2015-05-01 3:10 ` jb
2015-05-01 4:41 ` [Bloat] ThinkBroadBand also has a bloat detector in their speed test Rich Brown
2015-05-01 6:17 ` jb
2015-05-01 6:05 ` [Bloat] extremely good dslreports result for bufferbloat on free.fr Dave Taht
2015-05-01 6:31 ` jb
2015-05-01 8:10 ` Dave Taht
2015-05-02 11:49 ` Sebastian Moeller
2015-05-02 13:40 ` jb
2015-05-02 15:01 ` Sebastian Moeller
2015-05-02 16:55 ` Dave Taht
2015-05-02 17:15 ` Aaron Wood
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=CAH3Ss96JzO5mYyxFza9G6rKNOkT1OQxw+M_g32faLnuFxpFoJg@mail.gmail.com \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.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