mranton

via Dan Rayburn:

"""

My bullet point high-level thoughts on the Super Bowl stream:

- Numbers aren’t out yet, but I would expect an AMA number of under 9 million (2023 was 7 million AMA)

- While some were debating online if the Paramount+ stream was in 4K, it wasn’t. Their stream was 1080P 60fps true PQ HDR, had no color space conversions and was encoded for six bitrates maxing out at 12Mbps.

- Depending on the device and platform, I saw latency from 2 seconds to 60 seconds behind the TV broadcast feed

- HDR on Parmaount+ looked great across all devices I streamed on, and the upscaled 4K/HDR/5.1 stream on YouTube TV looked great as well

- Some users, including myself, did experience some errors or crashing of the stream, which started before kickoff and was largely mitigated before it could impact a larger portion of users. I put the impact to 1% or less of the total streams delivered.

- One media outlet reported, "The streaming platform seems to be struggling with all the Super Bowl traffic,” which was inaccurate. Paramount was prepared for the viewership they received, and there was no problem with the volume of users.

"""

bunny.net is a Slovenian global company with no affiliation with Russia.

The more CDN providers, the more choices you have for less money. If you are using Vultr as a hosting provider, it's much easier to enable/disable CDN out of the control panel.

everything works in our sandbox. We need a couple of customers to collect real data. I'll definitely going to post again with these numbers.

>Or, the site owner could manipulate the coordination JavaScript to report the downloaded file as invalid/corrupt/tampered with, and then just not re-request the file (and there's nothing you can do to stop them). So in that case, the site owner is managing to not pay for the service (assuming you don't bill for downloads that were reported as invalid).

This fraud is possible. We collect logs from three sources:

- the Balancer (belong to Farba)

- the Peer

- the User

We can analyze every single case of suspicious behavior.

for unpopular content, we will deploy a limited number of servers (belong to Farba) with a performant disk subsystem. A web cache storage is a separate option in every CDN: if you want your files always in "hot" cache, you have to pay extra.

to answer this question, I will write another article how we distribute cache among the Peers. Long story short:

- we divide web cache in buckets

- these buckets have different sizes

- we know a list of files in every bucket

- we know what buckets every Peer has

A customer can switch on/off regions. Also, they can set up a cap for every region. You can do it with regular CDNs as well, it's just a setting.