starred/qBittorrent

Fork 0

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

Limit bandwidth and share ratio by tracker #7866

New issue

Open

opened 2026-02-21 19:12:54 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 19:12:54 -05:00

Owner

Originally created by @Mike-EE on GitHub (Oct 4, 2018).

qBittorrent version and Operating System

N/A

If on linux, libtorrent and Qt version

N/A

What is the problem

N/A

What is the expected behavior

Per the title, there is a need to limit upload/download speed and ratio by tracker. This would be of high value as many users have limited ISP bandwidth to work with and tracker ratios to manage. This could be implemented by adding limit controls, similar to the individual torrent controls, to the tracker filter context menus.

Steps to reproduce

(type here)

Extra info(if any)

(type here)

Originally created by @Mike-EE on GitHub (Oct 4, 2018). ### qBittorrent version and Operating System N/A ### If on linux, libtorrent and Qt version N/A ### What is the problem N/A ### What is the expected behavior Per the title, there is a need to limit upload/download speed and ratio by tracker. This would be of high value as many users have limited ISP bandwidth to work with and tracker ratios to manage. This could be implemented by adding limit controls, similar to the individual torrent controls, to the tracker filter context menus. ### Steps to reproduce (type here) ### Extra info(if any) (type here)

deekerman added the

Feature request

label

2026-02-21 19:12:54 -05:00

deekerman commented

2026-02-21 19:12:56 -05:00

Author

Owner

@Mike-EE commented on GitHub (Dec 9, 2018):

Devs -

Any comments?

@Mike-EE commented on GitHub (Dec 9, 2018): Devs - Any comments?

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@thalieht commented on GitHub (Dec 9, 2018):

May be possible after #9939

@thalieht commented on GitHub (Dec 9, 2018): May be possible after #9939

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@saitoh183 commented on GitHub (Mar 4, 2019):

any change of this happening?

@saitoh183 commented on GitHub (Mar 4, 2019): any change of this happening?

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@Mike-EE commented on GitHub (Jun 19, 2019):

There is still a need for this feature. Is there anything that can be done to elevate the priority?

@Mike-EE commented on GitHub (Jun 19, 2019): There is still a need for this feature. Is there anything that can be done to elevate the priority?

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@Mike-EE commented on GitHub (Sep 12, 2019):

As we approach the one-year anniversary of this request, can the development team comment on the likelihood and timeline for implementation of this feature?

@Mike-EE commented on GitHub (Sep 12, 2019): As we approach the one-year anniversary of this request, can the development team comment on the likelihood and timeline for implementation of this feature?

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@Mike-EE commented on GitHub (Apr 26, 2020):

With all of the work being done on qBt and libtorrent, can we get some attention on this request? This is something that high-volume, multiple-tracker users need.

@Mike-EE commented on GitHub (Apr 26, 2020): With all of the work being done on qBt and libtorrent, can we get some attention on this request? This is something that high-volume, multiple-tracker users need.

deekerman commented

2026-02-21 19:12:58 -05:00

Author

Owner

@luzpaz commented on GitHub (Mar 14, 2025):

Related to #3650

@luzpaz commented on GitHub (Mar 14, 2025): Related to #3650

deekerman commented

2026-02-21 19:12:58 -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.)**