When you create a torrent and you're the only seeder, what download speed can you expect? Is there a way to optimise this? (sh.itjust.works)

submitted 6 months ago* (last edited 6 months ago) by hector@sh.itjust.works to c/piracy@lemmy.dbzer0.com

19 comments fedilink hide all child comments

As in, the download speed you provide to the peers.

top 19 comments

sorted by: hot top controversial new old

[-] bjoern_tantau@swg-empire.de 56 points 6 months ago

When you seed the download speed you can expect is 0 MB/s.

[-] hector@sh.itjust.works 0 points 6 months ago

I mean, the download speed you provide to the peers?

[-] cali_ash@lemmy.wtf 38 points 6 months ago

Depends on what upload speed your internet has.

[-] Rivalarrival@lemmy.today 36 points 6 months ago

Aka, your "upload" speed.

[+] hector@sh.itjust.works -37 points 6 months ago

Can you give a real answer instead of being pedantic about it? Jeez we’re not on Reddit fedora boy

[-] catloaf@lemm.ee 59 points 6 months ago

They did. "Your upload speed" is the answer.

[-] ShepherdPie@midwest.social 15 points 6 months ago

Do an internet speed test at someplace like speedof.me and whatever it gives you for "upload speed" is what you can expect to be the maximum.

[-] Steve@communick.news 14 points 6 months ago

Can you curb your sensitivity?
You used the wrong word. Maybe you didn't know. That's fine. We all do it occasionally. No harm.
Now that you know better, you could simply show some grace and humility by saying "Thank you". Then everyone could move on.

Have a good one

[-] Rivalarrival@lemmy.today 12 points 6 months ago

Not really, no.

When you understand how to ask the question, you will already have your answer.

Basically, your ISP, VPN, or your own networking equipment is going to be your chokepoint. The only person who can actually determine which one of those three is the slowest is... You. Nobody else has that information.

Until you can understand the distinction between "upload" and "download", you cannot understand the information your ISP, VPN, and the manufacturers of your networking equipment are providing to you.

(On a tangentially related note: If you don't have a VPN, go ahead and uninstall your torrent client until you've spent a lot more time studying networking concepts.)

[-] voracread@lemmy.world 33 points 6 months ago

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.

[-] hector@sh.itjust.works 7 points 6 months ago

Thanks super helpful :) gonna try that for my experiments

[-] Jolteon@lemmy.zip 7 points 6 months ago

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.

[-] voracread@lemmy.world 1 points 6 months ago

Ah, I have never seeded anything primarily. Still I thought as he was asking for things to check, I posted it.

[-] SubArcticTundra@lemmy.ml 8 points 6 months ago

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.

[-] retrieval4558@mander.xyz 5 points 6 months ago

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.

[-] IphtashuFitz@lemmy.world 3 points 6 months ago

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.