From: Dave Taht <dave.taht@gmail.com>
To: Sergey Fedorov <sfedorov@netflix.com>
Cc: Jonathan Foulkes <jf@jonathanfoulkes.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] this explains speedtest stuff
Date: Thu, 23 Apr 2020 13:27:14 -0700 [thread overview]
Message-ID: <CAA93jw4dbHu7z351yRjVp5Aps2EJ5sfC1yWQrz9QRx5SpqjS_Q@mail.gmail.com> (raw)
In-Reply-To: <CADN=VJ=c+yMCNKdzM3U08Ri8H1UOQ0eNdv8FYR2vKeJ1gfHQng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2646 bytes --]
On Thu, Apr 23, 2020 at 1:15 PM Sergey Fedorov <sfedorov@netflix.com> wrote:
> Hi folks,
>
> No need to put more pressure - I've seen Jonathan's suggestion and it
> makes a lot of sense to add the option to deep-link to an expanded version
> with all detailed parameters shown.
> This will be added some time this quarter (Q2), but not within a few next
> weeks.
>
that's wonderful, thanks!
One thing I've been seeing is way too many articles basically talking about
traffic increases (or not), and how many are videoconferencing from home...
but no metrics of import to videoconferencing folk. I've been engaged in a
conversation about increasing a certain videoconferencing platform's
default jitterbuffer to... wait for it... *1 sec* - based on how badly LTE
was performing for some people
so if you control your own videoconferencing tools, collecting more metrics
there would be usef
One very interesting metric a netflix streamer could be collecting is
differences in tcp RTT (assuming you slowed traffic down in europe,
especially, to a lower quality?), hour by hour, day by day.
another one is packet loss... retransmits...
> SERGEY FEDOROV
>
> Director of Engineering
>
> sfedorov@netflix.com
>
> 121 Albright Way | Los Gatos, CA 95032
>
>
>
> On Thu, Apr 23, 2020 at 1:00 PM Jonathan Foulkes <jf@jonathanfoulkes.com>
> wrote:
>
>> Confirmed, and I go there all time as well, you’d think it would be the
>> first thing Google would show us.
>>
>> At least Fast.com is on the first page, but they don’t pro-actively show
>> latency tests, especially on the upload.
>>
>> BTW- I’ve suggested they support a URL request format where we can
>> pre-set options that engage and show results for the bloat tests. This way
>> we can share that pre-formated link and the users who click on it
>> immediately see a bloat metric.
>> Maybe if a few more suggest this as well, it will climb in priority.
>>
>> - Jonathan
>>
>> > On Apr 23, 2020, at 3:38 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> >
>> > dslreports.com is only on the third page of the search results.
>> >
>> > https://www.google.com/search?q=internet+speed+test
>> > _______________________________________________
>> > 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
>>
>
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
[-- Attachment #2: Type: text/html, Size: 5517 bytes --]
next prev parent reply other threads:[~2020-04-23 20:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 19:38 Dave Taht
2020-04-23 20:00 ` Jonathan Foulkes
2020-04-23 20:15 ` Sergey Fedorov
2020-04-23 20:27 ` Dave Taht [this message]
2020-04-24 1:03 ` Sergey Fedorov
2020-04-24 0:44 ` Kenneth Porter
2020-04-24 0:47 ` Jonathan Morton
2020-04-24 1:16 ` Kenneth Porter
[not found] ` <6F1F3C646A7DFD2CC8C9E79E@172.27.17.193>
2020-04-24 1:20 ` Dave Taht
2020-04-24 5:15 ` Matt Taggart
2020-04-24 14:40 ` Kenneth Porter
2020-04-24 14:52 ` Sebastian Moeller
2020-04-24 14:56 ` Toke Høiland-Jørgensen
[not found] ` <mailman.56.1587740202.24343.bloat@lists.bufferbloat.net>
2020-04-24 15:22 ` Kenneth Porter
2020-04-24 16:22 ` Kenneth Porter
2020-04-24 18:43 ` Jonathan Morton
2020-04-25 1:16 ` Kenneth Porter
2020-04-25 8:43 ` Jonathan Morton
2020-04-25 13:49 ` Kenneth Porter
2020-04-25 14:00 ` Jonathan Morton
2020-04-25 14:14 ` Kenneth Porter
2020-04-25 14:19 ` Jonathan Morton
2020-04-25 15:31 ` Kenneth Porter
2020-04-25 15:33 ` Dave Taht
2020-04-25 15:32 ` Dave Taht
2020-04-25 15:43 ` Dave Taht
2020-04-25 15:59 ` Kenneth Porter
2020-04-25 16:06 ` Dave Taht
2020-04-25 16:22 ` Sebastian Moeller
2020-04-26 10:59 ` Toke Høiland-Jørgensen
2020-04-25 15:52 ` Kenneth Porter
2020-04-25 15:55 ` Dave Taht
2020-04-25 16:18 ` Kenneth Porter
2020-04-25 15:38 ` Kenneth Porter
2020-04-25 17:22 ` Y
[not found] ` <mailman.73.1587835496.24343.bloat@lists.bufferbloat.net>
2020-04-25 17:37 ` Jonathan Morton
2020-04-25 18:19 ` Dave Taht
2020-04-25 20:49 ` Kenneth Porter
[not found] ` <787FB38B9372372F376BB072@172.27.17.193>
2020-04-25 20:55 ` Dave Taht
[not found] ` <3D2F4A70BAB1774D1EFDC641@172.27.17.193>
2020-04-25 16:00 ` Dave Taht
2020-04-25 16:17 ` Kenneth Porter
2020-04-26 10:51 ` Toke Høiland-Jørgensen
2020-04-24 16:25 ` Kenneth Porter
[not found] ` <42D98FE80B7B9C1102C47579@172.27.17.193>
2020-04-24 16:32 ` Dave Taht
2020-04-24 16:39 ` Dave Taht
2020-04-24 17:42 ` Kenneth Porter
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=CAA93jw4dbHu7z351yRjVp5Aps2EJ5sfC1yWQrz9QRx5SpqjS_Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jf@jonathanfoulkes.com \
--cc=sfedorov@netflix.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