When I used to be a Netflix customer it was more the variability of my connection that was an issue and not its "speed" at a given optimal time.
Usually I could begin a stream without problems. But often while streaming (often enough for me to realize streaming was a bad experience) the bitrate dynamically dropped way down to a terrible quality in response to what I imagine were poor network conditions. Netflix no doubt sees this dynamic quality adjustment as a feature, and preferable to buffering, but I chose an HD stream and I'd rather even see an SD quality video that I could be sure would stay that quality than switching between HD and very low bitrate, fuzzy, artifacty video.
I don't blame Netflix for the quality of my connection, but streaming is just not as reliable as cable and it's not one of those Moore's Law type things where throwing more processing power or memory fixes the network issues.
Hi, I work on the streaming algorithms at Netflix.
You are correct that throughput variability matters a lot as well. The trouble is that the variability is somewhat unpredictable (at least, with our methods so far).
And you're also right that we view the "dynamic quality adjustment" as a feature! Without it, we wouldn't be able to serve both 0.5Mbps connections and 50Mbps connections seamlessly. But we don't like those sudden quality drops, either. We track how often that occurs, as well as how often rebuffers occur, and we work to eliminate both. We use large scale A/B testing to measure improvements in the field. If it's been a while since you tried it, I humbly suggest you consider trying it again. We've made a lot of progress.
If anyone is interested in working on this problem, we're currently hiring engineers on the Streaming Algorithms team with a focus on mobile. https://jobs.netflix.com/jobs/860465
Since I have you here, can I ask a random question? My kids love Puffin Rock, and it's the only show that I would have issues streaming. It would start out fine, but a few minutes into it start buffering and would take minutes; resume for a bit, then do the same thing.
When this happened I could switch to any other Netflix show or movie and it worked perfectly fine. When the kids whined, I'd switch back to Puffin Rock and the problem would persist.
So my question is: is it possible that either some shows are encoded differently so my player had trouble with it? Or is it that specific content was being messed with by my ISP?
The players in question were Roku 2 and 3, and my ISP is Charter (business plan). I haven't tried this in a few months since it got really annoying, but can try again if it helps.
Another Netflix engineer here - have you tried with something not popular? It may be that the other shows you checked were cached via OpenConnect but Puffin Rock wasn't.
My email is my username at netflix.com. If you can send me the email address connected to your account, I can see that your problem gets to the right people. (Disclaimer: I'm not on the OC or related teams directly)
I also have a question. According to fast.com, my connection is 270 mbp/s (which jives with the official 500 mbps I'm getting). Yet, I've noticed that on chrome on mac, when I launch a new show, it often starts at a very low bitrate and then gradually switch to a higher bitrate. The problem is that this happen on every episodes.
One workaround is using the ctrl-option-shift S combination and manually set the bitrate to the highest settings but it's still a bit annoying.
Have you tried the "Adjust your Netflix playback settings" advice at https://help.netflix.com/en/node/11559 ? Not that I haven't seen this adaptive stream behaviour, but I find it affects my mobile devices (like iPads) far more than on a wired, desktop computer.
You could also try it on a PC/laptop and then check other streaming servers (right CDN column) by pressing Ctrl-Alt-Shift-s. Or check the current stream quality / buffer state with Ctrl-Alt-Shift-d.
I'm frequently on a network that performs below 2.0 Mbps (with fast.com recording it as 2.0 Mbps, 1.6 Mbps, and 900 Kbps), generally with around 20% packet loss on the third hop (Verizon, now Frontier).
Netflix streams perfectly. It is astounding. No one else comes close. Amazon Video and YouTube work around half of the time, with rebuffering; video from anyone else—Vimeo, Apple, and any network's player included—is basically non-functional.
So, thank you all so much for excelling at what you do! It's very appreciated!
I'm working with some ISPs who are looking to understand how well NetFlix (and other services) are working on their networks in an attempt to improve service to their customers. These are small-ish ISPs, and I'm trying to help them move from guessing how well their customers are working based on high level traffic graphs to something more reliable and robust. I'd love to chat about this if you're available, email is in my profile.
It is a feature. When my kids (or parents) are watching and the stream suffers, I'd rather it step down the bitrate momentarily than cut the stream or pause to buffer.
Remember realnetworks and the constant "buffering.. buffering..". I'm glad to leave that in the past.
This highlights the conflict of interest that cable ISPs have. If they provide you good internet service, by either
allowing embedded Netflix (and Google, Amazon, etc) cache appliances into their network, or had add more downstream bandwidth, then you might have cut the cord. However, by giving you crappy internet service, they have retained you as a cable customer.
My service is fine for all other use cases but remote HD video, with its need for constant high bandwidth, is always going to be a fundamentally more difficult problem to solve than local digital video, traditional cable-delivered video, or regular downloads that can tolerate variance in transfer rate. It doesn't feel like it takes a conspiracy to explain that. When cable companies wanted to be our email or news/content portals I never had any issues using competing services on cable internet.
I was never going to cut the cord. I like having many channels and the serendipity of a wide variety of programming that's on "now" to choose from. There are shows/movies I never would have chosen myself but I stumbled onto them because they were "on" and they became favorites.
With a DVR I can also time-shift so I'm not tied to watching something on the broadcasters' schedule when I don't want to.
I tried Netflix to augment this with what I thought would be a big influx of other programming but it wasn't only the streaming experience I didn't like, I was unimpressed with the selection of the Netflix library. If they do another season of Arrested Development, I'll subscribe for a few months to support that.
Usually I could begin a stream without problems. But often while streaming (often enough for me to realize streaming was a bad experience) the bitrate dynamically dropped way down to a terrible quality in response to what I imagine were poor network conditions. Netflix no doubt sees this dynamic quality adjustment as a feature, and preferable to buffering, but I chose an HD stream and I'd rather even see an SD quality video that I could be sure would stay that quality than switching between HD and very low bitrate, fuzzy, artifacty video.
I don't blame Netflix for the quality of my connection, but streaming is just not as reliable as cable and it's not one of those Moore's Law type things where throwing more processing power or memory fixes the network issues.