Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
891–900 of 986 posts
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#892It's down permanently for me in India. We have Hotstar, which has a record of 58 million viewers during the cricket World Cup final. Way ahead.
Probably less about the level of advancement and more about their ability to stream vs play VOD. Two different kinds of infrastructure optimisation.
> https://www.icc-cricket.com/news/biggest-cricket-world-cup-e...
An impressive achievement and the scale netflix failed to do a year later.
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#893Seems like the magic number was 60 million concurrent streams https://www.theverge.com/2024/11/16/24298338/netflix-mike-tt...
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#894Earlier quoted context omitted.
> they want to be associated with "Faang" and yet their product is not really technology based. You lost me. Netflix built a massive CDN, a recommendation engine, did dynamic transcoding of video, and a bunch of other things, at scale, quite some years before everyone else. They may have enshittified in the last five years, but I dont see any reason why they dont have a genuinely legitimate claim to being a founder m…
Same thing was done a little later by HBO, Disney and a plethora of others, which points to the task not really being uber-difficult.
You can argue whether or not that edge translates into more revenue, but the edge is objectively there.
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#895Earlier quoted context omitted.
I think you’re oversimplifying it. Live event streaming is very different from movie streaming. All those edge cache servers become kinda useless and you start hitting peering bottlenecks.
Edge caches are not useless for live streaming. They're critical. The upstream from those caches has no way of handling each individual users. The stream needs to hit the edge cache and end users should be served from there. A typical streaming architecture is multi-tiered caches, source->midtier->edge. We don't know what happened but it's possible they ran out of capacity on their edge (or anywhere else).
> Even though widely used, this pattern has some significant drawbacks, the best illustration being the major incident that hit the BBC during the 2018 World Cup quarter-final. Our routing component experienced a temporary wobble which had a knock-on effect and caused the CDN to fail to pull one piece of media content from our packager on time. The CDN increased its request load as part of its retry strategy, making the problem worse, and eventually disabled its internal caches, meaning that instead of collapsing player requests, it started forwarding millions of them directly to our packager. It wasn’t designed to serve several terabits of video data every second and was completely overwhelmed. Although we used more than one CDN, they all connected to the same packager servers, which led to us also being unable to serve the other CDNs. A couple of minutes into extra time, all our streams went down, and angry football fans were cursing the BBC across the country.
https://www.bbc.co.uk/webarchive/https%3A%2F%2Fwww.bbc.co.uk...
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#896Earlier quoted context omitted.
I guess my question is: why? "Cable boxes" are uniformly awful to use in my experience. The UI is clunky, they take up space and it's another remote and another tangle of wires to try to hide. What advantage do they offer in 2024?
> What advantage do they offer in 2024? Live news and sports is huge for a ton of people. You have access to all the shows from the major networks. You don’t need to subscribe to Peacock and Paramount and Hulu and the TBS app and Discovery+ and… Better yet, they’re all combined in one interface as opposed to all trying to be the only thing that you use. Also, especially if you grew up with it, there is absolutely a s…
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#897Earlier quoted context omitted.
FIFA claimed the 2022 World Cup final reached 1.5 billion people worldwide, but again that seems like it was mostly via broadcast television and cable. As far as single stream, Disney's Hotstar claimed 59 million for last year's Cricket World Cup, and as far as the YT platform, the Chandrayaan-3 lunar landing hit 8 million. 100 million is a lot of streams, let alone 300. But also note that not every stream reaches a…
480p30 could be as high as 280mbit or as low as 280kbit. Same with other resolutions.
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#898Earlier quoted context omitted.
If you watch it over cable, you're live streaming it. Let's face it, that's where the vast majority of viewers see it. Few people view OTA even if the quality is better. Live sports do not broadcast the event directly to a streamer. They push it to their broadcast centers. It then gets distributed from there to whatever avenues it needs to go. Trying to push a live IP stream directly from the remote live venue rarely…
> If you watch it over cable, you're live streaming it. Those are multicast feeds. > Trying to push a live IP stream directly from the remote live venue rarely works as expected. In my experience it almost always works as expected. We have highly specialized codecs and equipment for this. The stream is actively managed with feedback from the receiver so parameters can be adjusted for best performance on the fly. Redu…
> We use fixed point links and satellite where possible because we own the whole pipe.
Over long distance I get better reliability out of a decent internet provision than in many fixed point to point links, and certainly when comparing at a price point. The downside of the internet is you can't guarantee path separation - even if today you're routing via two different paths, tomorrow the routes might change and you end up with everything going via the same data centre or even same cable.
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#899Earlier quoted context omitted.
> they want to be associated with "Faang" and yet their product is not really technology based. You lost me. Netflix built a massive CDN, a recommendation engine, did dynamic transcoding of video, and a bunch of other things, at scale, quite some years before everyone else. They may have enshittified in the last five years, but I dont see any reason why they dont have a genuinely legitimate claim to being a founder m…
Same thing was done a little later by HBO, Disney and a plethora of others, which points to the task not really being uber-difficult.
Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson
#900Earlier quoted context omitted.
480p30 could be as high as 280mbit or as low as 280kbit. Same with other resolutions.
I mean, yes, but nobody streams RAW video in practice, and I can't imagine any users or service providers who'd be happy with that level of inefficiency. In general, it's safe to assume some reasonable compression (which, yes, is likely lossy).
I remember watching the last season of Game of Thrones on one streaming provider, which topped out about 3.5mbit but claimed it was "1080p".
Give me a 15mbit 640x480 over 3.5mbit of 1920x1080 for that type of material any day.