Live data from Hacker News

Building fast.com

techblog.netflix.com

141–150 of 180 posts

Re: Building fast.com

#141
post #110

Earlier quoted context omitted.

The only times I use my ISP's DNS servers are when I initially set up a computer and forget to change the settings.

Yeah but unless you tunnel your DNS traffic they can modify responses very easily. Not that this is super common yet.

Is this what DNSSEC is supposed to prevent?

Re: Building fast.com

#142
post #126

Earlier quoted context omitted.

Do you have any proof that running a cron job impacts internet performance?

I believe you replied to the wrong person. I never made that claim unless I am going crazy. speedtest-cli has a lot to offer as a tool

What did you mean "works great" for then? Just that your cron job works?

Re: Building fast.com

#143
post #60

This is beautiful. By using Netflix's actual CDN and requesting actual video files over HTTP, they're preventing ISPs from whitelisting fast.com without also whitelisting Netflix itself. Of course there'll be a game of cat-and-mouse with DPI, but it's a super-neat way of making it much harder for the ISPs to misrepresent actual video download speed...

Yeah right. Just wait until a user visits fast.com and unthrottle their connection for 20 minutes. I strongly suspect some ISPs already do that with speedtest.net.

We need a speedtest website hosted on tor :D Then ISPs won't be able to know when you visit the site.

Re: Building fast.com

#144
post #28

First, I thought why another speed test, then I saw that they link their results directly to speedtest.net (the reference) and finally, I realized that fast.com is so much faster in detecting the download speed (but lacks upload and ping). Not bad. EDIT: And they secured a fantastic domain.

Why not also measure upload speed? I get it, it's because their business model only requires people to download stuff. The current state of the internet is much like the old days, where only big corporations had the ability to "broadcast". So I'm not enthusiastic at all.

Measuring upload would require building out infrastructure to receive data streams with reasonable performance.

That's nontrivially hard compared to the download portion, where they can use their existing CDN.

Sure -- they didn't build out a fully featured internet connection monitor. But what they have built is a pretty good tool, especially for diagnosing Netflix or last-mile performance.

Re: Building fast.com

#145

First, I thought why another speed test, then I saw that they link their results directly to speedtest.net (the reference) and finally, I realized that fast.com is so much faster in detecting the download speed (but lacks upload and ping). Not bad. EDIT: And they secured a fantastic domain.

>EDIT: And they secured a fantastic domain.

Apparently they have slow.com as well.

Re: Building fast.com

#146
post #17

You can also run fast.com from the command-line: https://github.com/sindresorhus/fast-cli

Here's a quick oneliner I threw together that does pretty much the same thing for those of us that dont have/want npm and node:

  mkfifo /tmp/fast.com.test.fifo ;token=$(curl -s https://fast.com/app-ed402d.js|egrep -om1 'token:"[^"]+'|cut -f2 -d'"'); curl -s "https://api.fast.com/netflix/speedtest?https=true&token=$token" |egrep -o 'https[^"]+'|while read url; do first=${url/speedtest/speedtest\/range\/0-2048}; next=${url/speedtest/speedtest\/range\/0-26214400};(curl -s -H 'Referer: https://fast.com/' -H 'Origin: https://fast.com' "$first" > /tmp/fast.com.test.fifo; for i in {1..10}; do curl -s -H 'Referer: https://fast.com/' -H 'Origin: https://fast.com'  "$next">>/tmp/fast.com.test.fifo; done)& done & pv /tmp/fast.com.test.fifo > /dev/null; rm /tmp/fast.com.test.fifo

Re: Building fast.com

#147
I wonder if Netflix makes it as easy to apply for their local CDN nodes as google does with GGC. I know akamai is super difficult to apply for and get admitted.

Ever since Netflix became available in our country we have been hurting BW wise. We don't throttle BW for any sites. Does anyone here have any experience with open connect (Netflix)?

Re: Building fast.com

#148
post #147

I wonder if Netflix makes it as easy to apply for their local CDN nodes as google does with GGC. I know akamai is super difficult to apply for and get admitted. Ever since Netflix became available in our country we have been hurting BW wise. We don't throttle BW for any sites. Does anyone here have any experience with open connect (Netflix)?

It doesn't seem terribly difficult so long as you have the traffic numbers to support it (peak traffic of 5gbps) and enough bandwidth for the box to fill its cache during off peak hours.

https://openconnect.netflix.com/en/requirements-for-deployin...

Re: Building fast.com

#149
Unfortunately, it doesn't work for me behind a proxy (tried with three different browsers). I thought I'd just check it out (https://fast.com - trying http redirects to https anyway), but it says:

"Could not reach our servers to perform the test. You may not be connected to the internet"

P.S.: It also bugs me that it says "the internet" and not "the Internet". :)

Re: Building fast.com

#150
post #97
post #69

Earlier quoted context omitted.

I'm also experiencing the same (also using HTTPS everywhere). Disabling the extension doesn't seem to work. If you get a solution, please let me know.

I found that Noscript was causing it. The best solution is to go into Noscript options > advanced > HTTPS and add .netflix.com to "Never force secure". The other way is to go into about:config and set noscript.httpsDefWhitelist to false. But that's less secure.

Ahhh! Thank you! That was my problem as well. I didn't even know NoScript was doing that. >:-(
Post reply on HN