4 ms·
YouTube has caching like that too, see: https://peering.google.com/#/ https://peering.google.com/#/ And https://peering.google.com/#/learn-more/faq https://p
by esprehn 3y ago
YouTube has caching like that too, see:
https://peering.google.com/#/ https://peering.google.com/#/
And
https://peering.google.com/#/learn-more/faq https://peering.google.com/#/learn-more/faq
And specifically the section on:
"What content can Google serve from an edge node?"
- crop_rotation 3y agoThis is not comparable to Netflix et al. YouTube catalog is effectively infinite, and people watch all kinds of random content. Storing 10k movies and 20k TV episodes is a cakewalk compared to this.
- hamandcheese 3y agoI don't disagree that YouTube has a much longer (and fatter) tail, but that doesn't mean they can't benefit from edge caching.
- crop_rotation 3y agoThey can benefit for sure, my point is that serving a YouTube type catalog is just far more expensive.
- acdha 3y agoThere's undoubtably more data being served but I'd be very curious how the edge caching efficiencies differ given how many people watch the same things (recommended by the algorithm) and since YouTube's content is so much shorter on average that larger catalog is somewhat balanced by any given cache node being able to hold more videos.
- lokar 3y agoThe cache hit rate is actually pretty high. Also, google already has setups at pops for other reasons and can cache fill at lower qos for free much of the time.