Opened 8 years ago
Last modified 5 months ago
#818 new enhancement
Adding superseed to i2psnark
| Reported by: | immense | Owned by: | zzz |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | apps/i2psnark | Version: | 0.9.4 |
| Keywords: | i2psnark superseed | Cc: | k1773r |
| Parent Tickets: | Sensitive: | no |
Description
Meaning, when the user is the only seed and there is more than one peer, avoid sending the same piece twice. This improves all peers' download rates, since it makes the peers more useful to each other. See http://www.bittorrent.org/beps/bep_0016.html for details.
Subtickets
Change History (8)
comment:1 Changed 8 years ago by
| Component: | unspecified → apps/i2psnark |
|---|---|
| Owner: | set to zzz |
comment:2 Changed 8 years ago by
| Milestone: | 0.9.5 → 0.9.9 |
|---|
comment:3 Changed 6 years ago by
to make full use of that feature:
after all pieces have been sent once and there are other torrents in i2p, the should be served then, so that the other peers complete among each other, withour the seeder having to send a single piece twice - ideally.
Exception should be if the user wants to upload the torrent as quickly as possible and maybe even leave after completion. In that case he should set the torrent priority to high and it should not "pause" it after the last unsent piece was sent.
comment:4 Changed 6 years ago by
| Milestone: | 0.9.9 |
|---|
comment:6 Changed 6 years ago by
darn, i had really overlooked this ticket here. And I had even commented here long time ago, lol.
So, sorry for the duplicate. But maybe/hopefully some of the considerations there are not totally nonsense and help mitigating the disadvantages of super seeding… 
comment:7 Changed 3 years ago by
| Cc: | k1773r added |
|---|
Sure, a reasonable request, and not the first time it's been suggested, although it's nice to have a ticket for it, thanks.
I've avoided it so far, both because it's low-priority, and it's also tricky to implement it correctly.
For example, although jrandom added rarest-first support to snark 6 or so years ago, it was completely broken until 0.9.3. So only in the last couple months has snark even minimally reduced the seeder bandwidth.