3 ms·
> If this was the only active seed for a torrent and there was nobody else, that would really be a problem. An AWS connection is going to have WAY more bandwid
by bsder 5y ago
> If this was the only active seed for a torrent and there was nobody else, that would really be a problem.
An AWS connection is going to have WAY more bandwidth than everybody else in the system.
The bittorrent clients would prioritize the AWS seed and suck way more download off of it relative to everybody else in the swarm.
- toast0 5y ago> An AWS connection is going to have WAY more bandwidth than everybody else in the system. Depends on how popular the torrent is on a local level. Two people on the same LAN probably have better bandwidth to eachother than from AWS. Two people on the same ISP in the same metro might have better bandwidth to each other than AWS if their connections are symmetric or if their ISP has poor transit and peering. Maybe a handful of other scenarios, but even if most of the clients get most of the download from AWS, that's still better for your wallet than all of the clients getting all of the download from AWS.
- chalst 5y agoApparently torrenting from S3 did not work very well: https://news.ycombinator.com/item?id=27524963 https://news.ycombinator.com/item?id=27524963 > The tracker Amazon ran was really trigger happy to ban peers (I'm sure it saw tons of bad actors, but still, it made testing really painful especially if you were churning infohashes as you tested new objects). And the seed was somehow painfully slow. Never once did any of my test scenarios see faster downloads than just downloading from S3.