3 ms·
The idea of a CDN is that you don't route everything through Google's data centers, you just pretend to and fetch from a nearby mirror. This really does save y
by btilly 14y ago
The idea of a CDN is that you don't route everything through Google's data centers, you just pretend to and fetch from a nearby mirror. This really does save you bandwidth - a lot of bandwidth.
Having some of the mirrors you use for this be in people's homes is an interesting twist that I had not thought of.
- throwaway64 14y agothe thing is the route to any "mirror" that sat in a persons home would be through Google's network. This wouldn't save them any money.
- btilly 14y agoIt does save them money, which is why every large ISP does it. The fact that makes it work is that not all routes through Google's network are created equal. Routes that go to and from data centers go a longer distance, through more pieces of equipment, and include busy backbones that you do not want to get overloaded. Routes that stay in a local neighborhood go a short distance and put load on one router which should be able to take it, and totally skip the critical backbone. From the point of view of the network operator, going to a data center is slow and expensive. Keeping traffic inside a local neighborhood is fast and cheap. Thus they want as much traffic as possible to go the fast and cheap route. CDNs cache data on local mirrors, and routes traffic to them whenever possible because that is faster and cheaper than going all the way to a data center. Every large ISP does this, and it would be shocking if Google didn't follow suit. But actually caching data on hardware that is sitting at customer's houses is an interesting twist.
- tonfa 14y agoYes, and putting a CDN node where the fiber terminates seems much much simpler (they might already do it for TV feeds anyway).
- nostrademons 14y agoWhy stick the mirror in the customer's home, though, where you have to mirror it once per customer? It basically becomes the same as a browser cache then. The logical place for it would be the local switching office (or whatever the equivalent is for fiber technology) - no idea if that's how it actually works, but that's where my naive knows-little-about-networking-besides-the-TCP/IP-stack mind would put it.
- btilly 14y agoThe idea is that one customer's request could be served off of a mirror sitting at another customer's home. The saving compared with putting it at a local switching office is that you don't need to buy a set of special machines and hard drives that sit at that office. Instead you're leveraging underutilized machines that people have already paid you for that are sitting at their houses. As far as the rest of the network is concerned, the traffic doesn't need to go to them so they are happy.
- philwelch 14y agoAnd with an uplink speed that equals your downlink, this peer-to-peer CDN becomes even more practical.
- nostrademons 14y agoThat seems highly inefficient, though. Now the request has to go up to the switching office and back down to another customer's home, instead of just up to the switching office. Why not just stick the cache at the switching office and eliminate one of those hops, cutting out some latency too? Disk and even memory are cheap...hell, as Patrick's preso pointed out, one of the main reasons for this project is that bandwidth performance is not increasing nearly as fast as CPU, disk, and memory.
- btilly 14y agoIt is less efficient on time. But the speed of light delays back and forth over your local network are still much better than the time it takes to go anywhere interesting - like a data center. So it is still a win for a consumer. (Albeit less of one than having a separate set of equipment in your office just for caching stuff.)
- devicenull 14y agoBut that's not how fiber works. At some point, it still has to go back to a central office. You can't just connect to your neighbors directly, it all ultimately goes through a switch/router somewhere.