Re:Spotify – Large Scale, Low Latency, P2P Music-on-Demand S...
by sp332 on Sunday May 29, 2011 @12:30PM
(#2596900)
I'm not sure I understand - the data has to come from somewhere, and go somewhere. If both endpoints are on the same last-mile ISP, the ISP wins because there's less traffic to and from peers, so their peering costs are lower. Other than that, why would it matter if the data came from a central server or from some other PC?
[ Parent
| on HN ]
Re:Spotify – Large Scale, Low Latency, P2P Music-on-Demand S...
by xtacy on Sunday May 29, 2011 @12:42PM
(#2596926)
I agree that if the end points are inside the ISP, it's good.
But peering is different from transit; peering is a delicate relationship where ISPs route traffic to each other for "free", as long as the demands are not too asymmetric. If this software results in a lot of traffic generated from a peering ISP, then it could be causes of worry for the receiving ISP.
Re:Spotify – Large Scale, Low Latency, P2P Music-on-Demand S...
by sp332 on Sunday May 29, 2011 @12:47PM
(#2596942)
But the "receiving" ISP is only receiving the data because its users asked for it. It doesn't make a difference if the data comes from a Spotify server or from a PC. It's still the same amount of data being transferred.
Re:Spotify – Large Scale, Low Latency, P2P Music-on-Demand S...
by wmf on Sunday May 29, 2011 @02:56PM
(#2597226)
Receiving data over a transit connection may be more expensive than from a CDN. In DOCSIS networks, P2P also tends to introduce last-mile upstream congestion which is expensive to fix.