From: moeller0 <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] anyone have info on the netflix speed test (fast.com)?
Date: Thu, 19 May 2016 11:03:44 +0200 [thread overview]
Message-ID: <873F9A0B-A0B6-44A6-A832-6CC35DAD5715@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1605190148340.20742@nftneq.ynat.uz>
Hi David.
> On May 19, 2016, at 10:50 , David Lang <david@lang.hm> wrote:
>
> On Thu, 19 May 2016, moeller0 wrote:
>> […]
>> This looks like marketing PR somehow inflicted the release of an internal demo. I agree with jb the one thing it has going for it is a short name… It does only one thing but does that a) badly and b) arguably it only even does 1/2 thing as ingress and egress are simply not completely independent. Arguing that Ping (RTT) and jitter are “network engineer’s analysis and diagnostic” tools and hence out of scope for their simple tool shows that they are aiming to low (I would go as far as claiming that with the explaining text the aim is still on the “own foot” territory, but I digress).
>
> I guess one thing that it does is shows anyone who is targeting netflix with slowdowns (or just not upgrading to meet capacity needs) where the problem is.
Mmmh, you are generous. In my eyes it does not even show this
>
> And since this is netflix, they really do only care about download speed :-(
>
> they should care about download speed while also doing an upload, to prevent pauses.
That is my point, you can and should try to simplify things but you will reach a “cliff” after that you are not simplifying but “stupidifying” (if there is such a word); and the quest for one reportable number is deep in not-clever territory in my eyes… (not that netflix should care about my sentiments)…
Best Regards
>
> David Lang
prev parent reply other threads:[~2016-05-19 9:03 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
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 [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=873F9A0B-A0B6-44A6-A832-6CC35DAD5715@gmx.de \
--to=moeller0@gmx.de \
--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