When you create a torrent and you're the only seeder, what download speed can you expect? Is there a way to optimise this?
When you create a torrent and you're the only seeder, what download speed can you expect? Is there a way to optimise this?
As in, the download speed you provide to the peers.
When you seed the download speed you can expect is 0 MB/s.
I mean, the download speed you provide to the peers?
Make sure that you are seeding random blocks instead of serial. That way peers who have a different block will exchange among themselves rather than waiting for you to provide each and every piece.
Thanks super helpful :) gonna try that for my experiments
This is the default behavior for most torrent clients. The only time it is not, is when the downloader on the other end has their torrent client manually set to download the torrent sequentially.
Ah, I have never seeded anything primarily. Still I thought as he was asking for things to check, I posted it.
As another poster has said, your internet package probably has an advertised upload speed beside your download speed (which is what people are usually interested in). Since you will be sending pieces of your torrent accross the internet, I think this will be the main speed bottleneck you will face. This will obviously also be split between however many leechers download your torrent at once. But given the p2p nature of torrents, the number of people downloading ddirectly from you should be much smaller than the number of people downloading the torrent altogether.
It depends on a lot of things. On your end you can make sure you're "connectable" and have the right ports open, and have a decent internet connection. Beyond that there's not much to do.
As far as BitTorrent itself goes, your optimal speed is also going to depend a bit on your client and the number of peers in the swarm.
Suppose you’re seeding a file to 3 peers. It’s not very efficient if your client uploads part 1 of your file to each peer, then uploads part 2 to each peer, etc. A more optimized upload would upload part 1 to peer A, part 2 to peer B, part 3 to peer C, etc. Then the peers can share each of those parts with each other. This way you are effectively only uploading the file one time before other nodes start seeding as well.
The thing is, this sort of seeding only works well in specific situations, including when there’s only one seeder, etc. And not all clients support this. Take a look at qbittorrent’s super seeding option for an example of one client that does.
3 Mbps