Maximize Queue Bandwidth Allocation #14117

New issue

Open

opened 2026-02-22 00:42:40 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 00:42:40 -05:00

Owner

Originally created by @Snake883 on GitHub (Dec 16, 2022).

Suggestion

I would like the queue to maximize the full available network bandwidth, in addition to queue priority.
Allocate as much network bandwidth to the queue priority.
Maximize bandwidth priority by queue rank.
Maximum network capacity can be determined by network speed test, or by monitoring QBT download speeds.
Queue adjustments will need to be made as seeders/peers fluctuate.

Example:
In the queue, if torrent #1 is not maximizing the download rate, then include downloading torrent #2.
Continue to include additional torrents by queue rank if maximum network bandwidth is below capacity.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @Snake883 on GitHub (Dec 16, 2022). ### Suggestion I would like the queue to maximize the full available network bandwidth, in addition to queue priority. Allocate as much network bandwidth to the queue priority. Maximize bandwidth priority by queue rank. Maximum network capacity can be determined by network speed test, or by monitoring QBT download speeds. Queue adjustments will need to be made as seeders/peers fluctuate. Example: In the queue, if torrent #1 is not maximizing the download rate, then include downloading torrent #2. Continue to include additional torrents by queue rank if maximum network bandwidth is below capacity. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

label

2026-02-22 00:42:40 -05:00

deekerman commented

2026-02-22 00:42:47 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 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 25, 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.)**