Serving Netflix Video Traffic at 400Gb/S and Beyond (2022) [pdf]
14 points
by tosh
1 hour ago
| 3 comments
| nabstreamingsummit.com
| HN
shanemhansen
3 minutes ago
[-]
Just an interesting observation I had about this once when I noticed that kernel quic implementations weren't very fast.

KTLS is mostly useful if paired with sendfile (I'm ignoring io_uring because I'm not as up to date on that). Otherwise you have to context switch back to userspace constantly.

reply
comment0r
45 minutes ago
[-]
Assuming the files are encrypted anyway for DRM reasons: why should static content like movies be TLSed? I know I know, "TLS all the things", but it sounds like a high cost at Netflix scale.
reply
xxpor
19 minutes ago
[-]
Stops Comcast from seeing the metadata and knowing exactly what their mutual customers are streaming.
reply
booi
9 minutes ago
[-]
wait till you hear about what smart tvs do..
reply
the-smug-one
5 minutes ago
[-]
I refused to connect my TV to the internet and use a Vero V for all of my watching needs. The Vero V is absolutely worse than most other experiences, but I'm happy.
reply
keane
7 minutes ago
[-]
To prevent a browser mixed content warning
reply
monocasa
31 minutes ago
[-]
It seems like it took engineering work, but TLS isn't their bottleneck when the data flow is structured correctly for the hardware (which is kind of the thesis of a lot of the Netflix CDN node optimization stuff).
reply
DeathArrow
18 minutes ago
[-]
Nice seeing BSD s getting some use.
reply