From: jb <justin@dslr.net>
To: David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] anyone have info on the netflix speed test (fast.com)?
Date: Thu, 19 May 2016 12:59:27 +1000 [thread overview]
Message-ID: <CAH3Ss961TCbzoZ9hj-Vkg55FyFwCTXZV1GHttgqg4Du-X75P9g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1605181250150.4130@nftneq.ynat.uz>
I had a quick look, it just does some parallel XHR fetches over port
80 from their server, which at least ( for me ) was not located at my
nearest amazon/netflix POP, but is located in the USA at a 200ms ping
time, so the speed reading was slow to ramp up, and lower than it
should be.
They instrument it and collect info but only report the download speed
to the user in megabits. I'm following a topic in neogaf in which
various people are running it, and it either gives about the same
result as speedtest.net or a lessor result (probably if the user is
further from california).
They may start adding local servers or may not. It doesn't measure or
report latency or upload speed or anything else. Its main virtue is
the short domain name, and that it starts immediately on page load,
and finally because it is quite simple, it has wider browser
compatibility.
On Thu, May 19, 2016 at 5:51 AM, David Lang <david@lang.hm> wrote:
> /. is talking about a new speed test to show your download speed. It doesn't
> show upload speeds or ping time.
>
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-05-19 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 19:51 David Lang
2016-05-19 2:59 ` jb [this message]
2016-05-19 11:56 ` [Bloat] [Bulk] " David Collier-Brown
2016-05-19 12:35 ` jb
2016-05-19 8:41 ` [Bloat] " moeller0
2016-05-19 8:50 ` David Lang
2016-05-19 9:03 ` moeller0
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=CAH3Ss961TCbzoZ9hj-Vkg55FyFwCTXZV1GHttgqg4Du-X75P9g@mail.gmail.com \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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