3speak has been using Bunny CDN for years, as far as I know, so the content delivery, if it can be catched, is not an issue. That said, videos can only be pulled if requested, as you probably know, thus the initial request for a video is key.
Since everything has been running off 1 Server, and that server has been doing everything. I do mean everything. The bottleneck I needed to address was obvious.
Now we got.
- Huge server - long term storage
- Fast, small server - new/fresh/hot videos for quick delivery to the CDN
- Bunny CDN to take it the rest of the way
If to that, we add other hotnodes, smaller nodes, with good internet connection, mind you, then we can have the initial lookup for new/hot videos feel almost instant.
If you remember on 3speak, sometimes you would hit play and you had to wait minutes for it to start.
The Server had to search millions of CID records to find the one HLS structure it was being asked. If to that you add it was receiving new videos, staging videos for the encoders, and serving videos too. It was almost a miracle it worked at all.
RE: Scaling 3Speak: Introducing IPFS Hot Nodes & the Traffic Director - Time to Upgrade your Encoder Nodes