Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

sportingnews.com

Post reply on HN
Print view View original

391–400 of 986 posts

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#391

Post by vitus »

nonameiguess wrote: post #387
margaretdouglas wrote: post #302

Earlier quoted context omitted.

Has there ever been a 300m concurrent live stream? I thought Disney+ had the record at something like 60m.

There's no way 300 million people watched this, especially if that number is representing every Netflix subscriber. The largest claimed live broadcast across all platforms is last year's Super Bowl with 202 million unique viewers for at least part of it, but that includes CBS, Nickelodeon, and Univision, not just streaming audiences. Its average viewers for the whole game was 123 million, which is second all-time to…

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 single individual.

And, as far as the 59 million concurrent streams in India, the bitrate was probably very low (I'd wager no more than 720p on average, possibly even 480p in many cases). It's again a very different problem across the board due to regional differences (such as spread of devices, quality of network, even behavioral differences).

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#392

Post by rjh29 »

bryanrasmussen wrote: post #343
rjh29 wrote: post #326

Earlier quoted context omitted.

Which would be doubly silly as peanuts aren't actually nuts.

I think acting as if peanuts are actually nuts for purposes of communication is much more defensible than acting as if tomatoes are vegetables, in short you are dying on a hill that was paved over long ago.

I agree most people will conflate them, but someone who's allergic to peanuts but not tree nuts (or vice versa), i.e. the people the labels are intended for, are going to care about the difference.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#393

Post by vitus »

new_user_final wrote: post #372

I am curious about their live streaming infrastructure. I have done live streaming for around 100k concurrent users. I didn't setup infrastructure because it was CloudFront CDN. Why it is hard for Netflix. They have already figured out CDN part. So it should not be a problem even if it is 1M or 100M. because their CDN infrastructure is already handling the load. I have only work with HLS live streaming where playlist…

> Why it is hard for Netflix. They have already figured out CDN part. So it should not be a problem even if it is 1M or 100M. because their CDN infrastructure is already handling the load ... Note: I am not saying my 100k is same scaling as their 100M. I am curious about which part is the bottleneck.

100k concurrents is a completely different game compared to 10 million or 100 million. 100k concurrents might translate to 200Gbps globally for 1080p, whereas for that same quality, you might be talking 20T for 10 million streams. 100k concurrents is also a size such that you could theoretically handle it on a small single-digit number of servers, if not for latency.

> CloudFront also has a feature request collapsing that greatly help live streaming.

I don't know how much request coalescing Netflix does in practice (or how good their implementation is). They haven't needed it historically, since for SVOD, they could rely on cache preplacement off-peak. But for live, you essentially need a pull-through cache for the sake of origin offload. If you're not careful, your origin can be quickly overwhelmed. Or your backbone if you've historically relied too heavily on your caches' effectiveness, or likewise your peering for that same reason.

200Gbps is a small enough volume that you don't really need to provision for that explicitly; 20Tbps or 200Tbps may need months if not years of lead time to land the physical hardware augments, sign additional contracts for space and power, work with partners, etc.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#394

Post by johnisgood »

throwawaythekey wrote: post #377
normie3000 wrote: post #304

Earlier quoted context omitted.

> well known cases of particular employers who select for overpaid employees Not well-known enough, apparently. Where should I be applying?

There are different forms of overpayment but to give some examples: - The recent story of AWS using serverless for video processing comes to mind [1]. - Google is renowned for rest and vest. - Many government jobs pay more than their private counterparts. - Military contractors - Most of the healthcare industry - Lobbyists [1] https://news.ycombinator.com/item?id=35811741

In terms of healthcare industry in Hungary: one worker does the same job for 700 USD a month and another for 1100 USD, the only difference is formal education and years worked in the industry. You can perform much better (by actually caring about the patients in those 12 hours you work) but you will get paid the same amount regardless. Of course if you have 3 kids (whether they are adults or not) then you do not pay taxes (or much less than someone who does not have kids or only has 2).

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#395

Post by ethbr1 »

YZF wrote: post #350
ethbr1 wrote: post #159

Earlier quoted context omitted.

I'm curious if the root cause is more variable than usual latency. Sample size 1, but... I saw a ton of buffering and failure on an embedded Netflix app on a TV, including some infinite freezes. Moved over to laptop, zero buffering. I assume the web app runs with a lot bigger buffer than whatever is squeezed into the underpowered TV.

Likely these devices use different media formats and/or quality levels. And yes, it's possible one device buffers more than the other. Infinite freezes sounds like some routing issues or bugs.

When I was watching the behavior on the tv, was wondering if buffering sends some separate, non-business-as-usual requests, and that part of Netflix's delivery architecture was being overloaded.

E.g. "give me this previous chunk" vs "send me the current stream"

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#396

Post by horns4lyfe »

briansm wrote: post #314
AdieuToLogic wrote: post #175

Earlier quoted context omitted.

> I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Apparently he was smart enough to get away from the Fortune 500 company he worked at, reporting to yourself, and "got a pay raise too." > Our engineers are fucking morons. And this guy was the dumbest of the bunch. See above. > If you think Netflix hires top tier talent, you don't know Net…

White-Knighting for 'fucking morons' is not a good look though. You'll end up in a world where packets of peanuts have a label on saying 'may contain nuts'.

And you think white knighting for managers who call their directs all “fucking morons” is a good look?

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#397

Post by horns4lyfe »

_giorgio_ wrote: post #356
walrushunter wrote: post #56

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

I don't understand why nobody here believes you. There's no reason to doubt what you say, probably people identify with the mistreated one. Why?

Because the idea that all the engineers that work at his large company are morons is absurd. Anyone in that situation that believes that and even more, states it, is just making their own character flaws apparent.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#398

Post by horns4lyfe »

walrushunter wrote: post #56

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

Sounds like you’re a good match for their team then

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#399

Post by emeril »

barkingcat wrote: post #67
jeromegv wrote: post #47

Earlier quoted context omitted.

Not the same demographic but their last large attempt at live was through a Love is blind reunion. It was the same thing, millions of people logging in, epic failure, nothing worked. They never tried to do a live reunion again. I suppose they should have to get the experience. Because they are hitting the same problems with a much bigger stake event.

yup wanted to say that live stream stuttering has happened before on Netflix - I don't think the reputation is deserved. From a livestreaming standpoint, netflix is 0/x - for many large events such as love is blind, etc. From a livestreaming standpoint, look to broadcast news, sports / Olympics broadcasters, etc and you'll see technology, equipment, bandwidth, planning, and professionalism at 1000x of netflix. Heck,…

All valid points though each of those examples seemingly only has a fraction of the viewers of the netflix events, right?

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#400

Post by fragmede »

strken wrote: post #360
Lammy wrote: post #145

Earlier quoted context omitted.

I hope to never have a manager who is mentally stack ranking me and my coworkers in terms of perceived dumbness instead of in terms of any positive trait.

I'm not a manager and I don't stack rank people, but I am 100% capable of knowing when one of my co-workers or predecessors is a fucking moron. The trick is to use my massive brain to root cause several significant outages, discover that most of them originate in code written by the same employee, and notice that said employee liked to write things like // @ts-nocheck // obligatory disabling of typescript: static typ…

I dunno, I've gone and done a "git blame" to find out who the fucking moron that wrote the code was, only to find out it was me three years ago.

Sure, there's such a thing as stupid code, but without knowing the whole context under which a bit of code was produced, unless it's utterly moronic, (which is entirely possible, dailywtf has some shiners), it's hard to really judge it. Hindsight, as applied to code, is 2020.

Post reply on HN