starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

download first part first #2661

New issue

Closed

opened 2026-02-21 16:20:31 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-21 16:20:31 -05:00

Owner

Originally created by @siran on GitHub (Jun 18, 2015).

I don't understand the logic: why when "downlaod in sequential order" is selected, then "download first and last pieces first" is ALSO selected? Sequential order is mostly for streaming, so why would someone want to use download time to download the last part?

I think that "download first AND last pieces" should be in any case optional, the default being ONLY sequential order.

Also I don't understand whydo I have to choose this option ("download in sequential order") for EACH torrent instead of it being configurable in the global preferences?

Originally created by @siran on GitHub (Jun 18, 2015). I don't understand the logic: why when "downlaod in sequential order" is selected, then "download first and last pieces first" is ALSO selected? Sequential order is mostly for streaming, so why would someone want to use download time to download the last part? I think that "download first AND last pieces" should be in any case optional, the default being ONLY sequential order. Also I don't understand whydo I have to choose this option ("download in sequential order") for EACH torrent instead of it being configurable in the global preferences?

deekerman

2026-02-21 16:20:31 -05:00

closed this issue
added the
Feature request
label

deekerman commented

2026-02-21 16:20:37 -05:00

Author

Owner

@chrishirst commented on GitHub (Jun 19, 2015):

so why would someone want to use download time to download the last part?

Because not ALL file types have the 'header' in the first section of the file, AVI 'headers' for example are at the end of the file

@chrishirst commented on GitHub (Jun 19, 2015): > so why would someone want to use download time to download the last part? Because not ALL file types have the 'header' in the **first** section of the file, AVI 'headers' for example are at the **end** of the file

deekerman commented

2026-02-21 16:20:37 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 19, 2015):

Most modern file formats have the header and index at the beginning of the file but AVI is a very common format and it has at the end.

Maybe we can make a list of file formats with the index at the and and just check the "download first AND last pieces" option for that formats.

@ngosang commented on GitHub (Jun 19, 2015): Most modern file formats have the header and index at the beginning of the file but AVI is a very common format and it has at the end. ![](http://www.ezr8.com/images/format/avi/a_1.png) Maybe we can make a list of file formats with the index at the and and just check the "download first AND last pieces" option for that formats.

deekerman commented

2026-02-21 16:20:37 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Jun 19, 2015):

For anyone who is interested: misc.cpp#L273.

@Chocobo1 commented on GitHub (Jun 19, 2015): For anyone who is interested: [misc.cpp#L273](https://github.com/qbittorrent/qBittorrent/blob/f89c44e1a06226352753a42b13d34c52501456d9/src/core/utils/misc.cpp#L273).

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 19, 2015):

Also I don't understand whydo I have to choose this option ("download in sequential order") for EACH torrent instead of it being configurable in the global preferences?

We need that option.

@ngosang commented on GitHub (Jun 19, 2015): > Also I don't understand whydo I have to choose this option ("download in sequential order") for EACH torrent instead of it being configurable in the global preferences? We need that option.

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@chrishirst commented on GitHub (Jun 19, 2015):

Because sequential downloading is BAD for the 'health' of a swarm, therefore the LESS it is used the better.

@chrishirst commented on GitHub (Jun 19, 2015): Because sequential downloading is **BAD** for the 'health' of a swarm, therefore the LESS it is used the better.

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@siran commented on GitHub (Jun 19, 2015):

should I close this? thank you all for your insights!

@siran commented on GitHub (Jun 19, 2015): should I close this? thank you all for your insights!

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 19, 2015):

Because sequential downloading is BAD for the 'health' of a swarm, therefore the LESS it is used the better.

I don't totally agree. It is bad for the swarm only if there are very few seeds (1 or 2 seeds). Otherwise it is indistinct because you end up having all the pieces.

@ngosang commented on GitHub (Jun 19, 2015): > Because sequential downloading is BAD for the 'health' of a swarm, therefore the LESS it is used the better. I don't totally agree. It is bad for the swarm only if there are very few seeds (1 or 2 seeds). Otherwise it is indistinct because you end up having all the pieces.

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@siran commented on GitHub (Jun 24, 2015):

I have to reopen this, because the fact that "downloading in sequential order" is bad for the swarm is kind of BS, as @ngosang says.

"Download in sequential order" should be the default value when a number of N seeds have 100% of the file. N should be configurable in options, but it can default to, let's say, 10.

Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense.

@siran commented on GitHub (Jun 24, 2015): I have to reopen this, because the fact that "downloading in sequential order" is bad for the swarm is kind of BS, as @ngosang says. "Download in sequential order" should be the default value when a number of N seeds have 100% of the file. N should be configurable in options, but it can default to, let's say, 10. Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense.

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 25, 2015):

Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense.

This problem is fixed in v3.3.0 (alpha).

@ngosang commented on GitHub (Jun 25, 2015): > Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense. This problem is fixed in v3.3.0 (alpha).

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@ngosang commented on GitHub (Apr 24, 2016):

Related #164.
@sledgehammer999 close. User problem was fixed.

@ngosang commented on GitHub (Apr 24, 2016): Related #164. @sledgehammer999 close. User problem was fixed.

deekerman commented

2026-02-21 16:20:38 -05:00

Author

Owner

@thalieht commented on GitHub (Jul 24, 2018):

siran commented on Jun 25, 2015:

I have to reopen this, because the fact that "downloading in sequential order" is bad for the swarm is kind of BS, as @ngosang says.

"Download in sequential order" should be the default value when a number of N seeds have 100% of the file. N should be configurable in options, but it can default to, let's say, 10.

Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense.

libtorrent now has an option to download sequentially if seeds/peers ratio is 10 or more and it's the default (for qBt as well)

Also original issue is solved so closing.

@thalieht commented on GitHub (Jul 24, 2018): [**siran**](https://github.com/siran) commented on [Jun 25, 2015](https://github.com/qbittorrent/qBittorrent/issues/3250#issuecomment-115082505 "null - Replied by Github Reply Comments"): > I have to reopen this, because the fact that "downloading in sequential order" is bad for the swarm is kind of BS, as @ngosang says. > > "Download in sequential order" should be the default value when a number of N seeds have 100% of the file. N should be configurable in options, but it can default to, let's say, 10. > > Also, if a fie is not currently downloading it is not possible to select "download in sequential order" which is nonsense. libtorrent now has an option to download sequentially if seeds/peers ratio is 10 or more and it's the default (for qBt as well) Also original issue is solved so closing.