Sequential mode should be more sequential #4841

New issue

Open

opened 2026-02-21 17:31:56 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 17:31:56 -05:00

Owner

Originally created by @SomeoneIsWorking on GitHub (Nov 3, 2016).

I get that it sacrifices sequentiality for speed but maybe there should be an option to force it to be more sequential.

Maybe with different modes like
Sequentiality enforcement on sequential downloads: ( ) Light, (*) Aggressive, ( ) Absolute

Originally created by @SomeoneIsWorking on GitHub (Nov 3, 2016). I get that it sacrifices sequentiality for speed but maybe there should be an option to force it to be more sequential. ![image](https://cloud.githubusercontent.com/assets/9450683/19977205/84687e3c-a1fb-11e6-9a6c-63103c006520.png) Maybe with different modes like Sequentiality enforcement on sequential downloads: ( ) Light, (*) Aggressive, ( ) Absolute

deekerman added the

Feature request

label

2026-02-21 17:31:56 -05:00

deekerman commented

2026-02-21 17:32:00 -05:00

Author

Owner

@thalieht commented on GitHub (Nov 3, 2016):

Feature request #182 should help when implemented and PR #5314 is a step (or all steps?) towards it.

@thalieht commented on GitHub (Nov 3, 2016): Feature request #182 should help when implemented and PR #5314 is a step (or all steps?) towards it.

deekerman commented

2026-02-21 17:32:00 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**