Try increasing the limit, to maybe a couple hundred at most.Įnable DHT if your client supports it. On the other side of the coin, your client may be limiting you too much. Chances are that your client is already set up this way, but I don't know what client you're using. Given the size of the swarms, it's easily possible to max out your OS's total number of TCP connections, and that can cause big problems.
Limit the total number of connections possible, if you can. I'm not entirely sure why that has an effect on your download speeds, but it definitely does. Make sure that your upload bandwidth isn't maxed out.
Dd wrt bittorrent transmission plus#
To summarize what other people have said, plus add a few notes of my own: Shall we all point our clients at those Max Headroom torrents and give it a go? The particiants would all agree to download that series over the course of the period, and continue to seed the torrent for the rest of the period. The community would work by, each week or fornight, selecting on a particular series to download, via some active torrent. Suppose a mailing list or LJ community was created for people who want to fetch old scifi TV shows. The popularity problem could be solved with a little organisation, given that the point of diminishing returns for active seeds and peers is probably about a dozen and a couple of hundred respectively. Though I wonder whether bittorrent's overall poor speed might be by design: using a client that isn't 'cheating', you're always uploading while you're downloading, so if downloads are artificially slower than they could be, you're forced to share for much longer, which kind of makes the whole thing work, I suppose. With bittorrent, that means throttling the upload rate and number of upload slots. The basic problem with peer to peer file sharing is everyone want's to download as fast as their big fat pr0n pipe will let them, but no one wants to share their bandwidth cap with strangers.
0 kommentar(er)
