Live data from Hacker News

Building fast.com

techblog.netflix.com

151–160 of 180 posts

Re: Building fast.com

#151
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)?

[deleted]

Re: Building fast.com

#152

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". :)

:D AP and other publishers don't recommend capitalising 'internet' and 'web'.

"The changes reflect a growing trend toward lowercasing both words, which have become generic terms"

http://www.poynter.org/2016/ap-style-change-alert-dont-capit...

Re: Building fast.com

#153

It's a little odd that they elected to invent their own way of requesting just a range of bytes in a file. It's built into HTTP: https://tools.ietf.org/html/rfc7233

As others have mentioned "ranges" are put in the uri stem & query string for two reasons; evading mangling proxies and simpler access from browsers/clients. From memory notable implementarions are MPEG DASH, action script/flash, icecast, and various proprietary "services".

The formats that send time ranges instead of bytes ranges are the worst. In that case the server/cdn has to retrieve & read the manifest, decode time indexes to fragments/chunks/ranges, and then return the appropriate byte stream to the player. This also means you cant cache based on the URI plus query string!

Source: ive worked at both ISPs and CDNs supporting streaming content

Re: Building fast.com

#154

Earlier quoted context omitted.

Makes sense but wouldn't they then use the netflix domain? Something like netflix.com/fast? I could image that if providers throttle it would be a mix of IPs and domain.

Some ISP's (we don't throttle anything) throttle based on several factors, mainly packet signatures. Traffic coming from big/known sources, such as Netflix, contain unique signatures (probably the headers, etc, that are unique to Netflix Traffic). You can then check all incoming packets that match those signatures and throttle them. So unless Netflix went out of their way to mask every request to look like video cont…

The connection is encrypted, the ISP can't see request headers. For the main data download, all they can determine is its an TLS connection to a netflix content server. Potentially you could do some stateful monitoring looking for recent requests to fast.com but it's generally much harder to implement than simple IP or SNI based profiling.

Re: Building fast.com

#155
Apparently my ISP upgraded my speeds; I tested at 170Mbps and when I last checked my plan it was 80Mbps.

In general, I've been quite happy with Cox. The actual network service is great. Customer service and pricing are so-so (I'm paying $60/mo. for the above connection; customer service is very hit-or-miss depending on which representative I get, but I haven't been outright lied to).

Re: Building fast.com

#156

Earlier quoted context omitted.

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?

Yes and no. It is what DNSCurve is designed to prevent.

Re: Building fast.com

#157

Earlier quoted context omitted.

This is a bit of an unfair test, as it is not in Netflix's best interest to provision enough CDN capacity for any user to hit 1Gbps, especially at peak times. Netflix wants to buy/provision just enough capacity so that users don't complain. Depending on the distribution of the users in the area, this could 5Mbps per user, or 15Mbps per user for a large amount of 4K streamers. Netflix pushes their CDN nodes to the lim…

That's incorrect. I have AT&T Gigapower 1GB connection, and fast.com shows me 850-989 MB/s speeds. It seems Netflix does shove info to you as fast as they can from fast.com

I'm not saying it isn't possible to ever hit 1Gbps (or whatever speed), I'm simply saying it is not in Netflix's best interests to make sure this is possible 24/7 365.

I have 1Gbps CondoInternet/WaveG at home, right now at 11PM PST I get ~400Mbps from Fast.com and 800Mbps+ from DSLReports and the Comcast/Xfinity speedtest.

Re: Building fast.com

#158
post #59
post #23

Earlier quoted context omitted.

200k is a pretty good sample size is it not? Even with multiple providers. Most election/political polls use far less data and very big decisions get made because of them.

Sample size is only a tiny part of the relevance of a sample. You can take a thousand gallons of water to test water quality, but if all of it is from the same faucet the sample isn't representative.

I don't see how that applies here though. How much variation is there among broadband users that matters?

Re: Building fast.com

#159
post #56

Earlier quoted context omitted.

Some ISP's (we don't throttle anything) throttle based on several factors, mainly packet signatures. Traffic coming from big/known sources, such as Netflix, contain unique signatures (probably the headers, etc, that are unique to Netflix Traffic). You can then check all incoming packets that match those signatures and throttle them. So unless Netflix went out of their way to mask every request to look like video cont…

The files that fast.com has you download ARE chunks of video files :)

Does anyone know which video the test file is?

Perhaps it's encrypted, or a Netflix promo piece.

Wouldn't there be copyright issues to use their actual streaming licences content?

Re: Building fast.com

#160
post #56

Earlier quoted context omitted.

The files that fast.com has you download ARE chunks of video files :)

Does anyone know which video the test file is? Perhaps it's encrypted, or a Netflix promo piece. Wouldn't there be copyright issues to use their actual streaming licences content?

Earlier I got curious and I was wondering this too. Seems to be a 'random' blob of bytes every time that doesn't decode, but then I remembered they serve DRM'ed video that is then decrypted on the client.
Post reply on HN