Less available pieces first #3669

New issue

Closed

opened 2026-02-21 16:53:59 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 16:53:59 -05:00

Owner

Originally created by @BLLuis on GitHub (Jan 3, 2016).

I use to download very rare files, so, they are with very low ratio, and it's normal for me that the file is not complete for a long time, a long time ago I had a partially download file for 3 and a half years.
I don't know if there are other people with my problems, but, is common for me.
Anyway, I think that an option to DOWNLOAD LESS SHARED PIECES FIRST will be a very good option, in my case, again, I don't know if I'm the only one with this kind of problem.
I see many times a file with 3 peers (for example) one peer has 20%, another 40% and the last one with a 100%, my computer download pieces (random or sequentially) from the three peers, at some point, the peer with 100% disappear (some times FOREVER, some other for 3 and a half year) and I'm left with a file that never will be completed, if an option like I comment before where available, my computer should download first the pieces from the peer with 100% that can't be found on the others peers.
Obviously that this is a wish, I don't know if the protocol or the rules allow this kind of behavior.

Thanks and sorry for my english.

Originally created by @BLLuis on GitHub (Jan 3, 2016). I use to download very rare files, so, they are with very low ratio, and it's normal for me that the file is not complete for a long time, a long time ago I had a partially download file for 3 and a half years. I don't know if there are other people with my problems, but, is common for me. Anyway, I think that an option to DOWNLOAD LESS SHARED PIECES FIRST will be a very good option, in my case, again, I don't know if I'm the only one with this kind of problem. I see many times a file with 3 peers (for example) one peer has 20%, another 40% and the last one with a 100%, my computer download pieces (random or sequentially) from the three peers, at some point, the peer with 100% disappear (some times FOREVER, some other for 3 and a half year) and I'm left with a file that never will be completed, if an option like I comment before where available, my computer should download first the pieces from the peer with 100% that can't be found on the others peers. Obviously that this is a wish, I don't know if the protocol or the rules allow this kind of behavior. Thanks and sorry for my english.

deekerman closed this issue

2026-02-21 16:54:02 -05:00

deekerman commented

2026-02-21 16:54:04 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 3, 2016):

That's what we do. We download rarest piece first. The "rarest first" algorithm is implemented by libtorrent(our backend).

If you see a bug then you should report it to libtorrent.

@sledgehammer999 commented on GitHub (Jan 3, 2016): That's what we do. We download rarest piece first. The "rarest first" algorithm is implemented by [libtorrent](https://github.com/arvidn/libtorrent)(our backend). If you see a bug then you should report it to libtorrent.

deekerman commented

2026-02-21 16:54:04 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 3, 2016):

In your case, the only seed probably disappears before the other peers have a whole torrent amongst them. Or you(or another peer) are downloading with custom file priorities or sequentially. Then the "rarest first" algorithm isn't applied.

@sledgehammer999 commented on GitHub (Jan 3, 2016): In your case, the only seed probably disappears before the other peers have a whole torrent amongst them. Or you(or another peer) are downloading with custom file priorities or sequentially. Then the "rarest first" algorithm isn't applied.

deekerman commented

2026-02-21 16:54:04 -05:00

Author

Owner

@chrishirst commented on GitHub (Jan 3, 2016):

see #3784 as well

@chrishirst commented on GitHub (Jan 3, 2016): see #3784 as well

deekerman referenced this issue

2026-02-21 18:26:51 -05:00

Language settings on windows are unreliable #6489