3 ms·
Terribly unlikely. AWS outbound bandwidth costs are outrageous. Nobody in their right mind would provision a BitTorrent that could suddenly give you a couple
by bsder 5y ago
Terribly unlikely. AWS outbound bandwidth costs are outrageous.
Nobody in their right mind would provision a BitTorrent that could suddenly give you a couple thousand dollar bill if your torrent suddenly got popular.
The possibly ridiculous bandwidth costs probably meant that absolutely nobody was using this.
- prvc 5y agoWhat would an economical alternative be?
- oauea 5y agoGrab a digital ocean VM for $5/month and call it a day. Should be enough for all your (legal) torrenting needs.
- jhgg 5y agoPlain ole bit torrent. Run some seed nodes on dedicated hardware with unmetered bandwidth. It'll get you pretty far.
- IggleSniggle 5y agoHow about: where the cost is amortized among sufficient uploading peers that it can be easily hosted on consumer home connections, despite very small upload rates available on consumer ISP connections?
- gopalv 5y ago> AWS outbound bandwidth costs are outrageous. The torrent would have been a way to get the data from peers instead of serving it purely from S3 outbound. If this was the only active seed for a torrent and there was nobody else, that would really be a problem. But otherwise, this should technically result in less outbound bandwidth usage than serving the whole file out of S3.
- deleted 5y ago[deleted]
- 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.
- foota 5y agoFraudulent billing is a problem for public cloud providers. In particular with hosting pirated or illegal content, so BitTorrent seems like a natural issue.
- NullPrefix 5y agoPirate content on a stolen AWS account is less likely than crypto miners.
- thekyle 5y agoIt seems to me that the worst case scenario for using BitTorrent is that S3 is the only seed and everyone downloads from that, however, I don't see how that is worse than the alternative which is to offer direct downloads from S3. In other words, from a costs perspective, the worst case scenario for BitTorrent is the best case scenario for direct download.