Optional minimum peer/seed upload speed #12326

Closed
opened 2026-02-21 22:36:10 -05:00 by deekerman · 1 comment
Owner

Originally created by @TheSparrowLenz on GitHub (Aug 6, 2021).

Feature request

Checklist

  • [ X] I have read the feature request section in the contributing guidelines, so I know how to submit a good feature request with the required information
  • [X ] I have verified that the feature I am requesting is not available in the latest version
  • [X ] (optional but recommended) I have verified that the feature I am requesting is not available in the latest CI build
  • [X ] I have checked the frequent/common issues list and searched the issue tracker for similar feature requests (including closed ones) to avoid posting a duplicate
  • [ X] This request is not a support request or question, both of which are better suited for either the discussions section, forum, or subreddit. The wiki did not contain a suitable solution either

Description

Suggestion

I have noticed that on popular torrents I sometimes download off of peers/seeds that upload at below KiB/s speeds. These peers/seeds in essence do not contribute to my downloading of the torrent, in fact they are hogging slots for other, faster peers/seeds to occupy.

I would suggest to have a minimal peer/seed upload speed (adjustable) option implemented so those peers/seeds can be discarded if they fail to reach the limit. By discarded I mean stripped from the ability to upload to you, but in the case of peers of course still allowed to download off of you.

This feature could be implemented on a global basis (global limit) but would be enforced on a per torrent basis. So if the peer/seed appears on another torrent with higher speeds, it doesn't get affected for that particular torrent.

I would argue that this enhances the distribution of the torrent (faster downloading allows for faster seeding when done) without being in danger of being labeled as a leech as you do not limit uploads, just downloads.

Makes sense?

Use case

all torrent downloads with qBittorrent

Extra info/examples/attachments

Screenshot104132

Originally created by @TheSparrowLenz on GitHub (Aug 6, 2021). # Feature request <!-- ############################################################################### WARNING! IGNORING THE INSTRUCTIONS IN THIS TEMPLATE WILL RESULT IN THE ISSUE BEING CLOSED AS INCOMPLETE/INVALID ############################################################################### --> ## Checklist <!-- ################################## IMPORTANT ################################## As you read and fulfill each of the following requirements below, put an "x" between the square brackets to mark each task as done, like so: [x] --> - [ X] I have read the **feature request section** in the [contributing guidelines](https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md), so I know how to submit a good feature request with the required information - [X ] I have verified that the **feature** I am requesting is **not available** in the **[latest version](https://www.qbittorrent.org/download.php)** - [X ] (optional but recommended) I have verified that the **feature** I am requesting is **not available** in the **[latest CI build](https://github.com/qbittorrent/qBittorrent/actions/workflows/ci.yaml?query=branch%3Amaster+event%3Apush)** - [X ] I have **checked the [frequent/common issues list](https://github.com/qbittorrent/qBittorrent/projects/2)** and **searched** the issue tracker for similar feature requests (including closed ones) **to avoid posting a duplicate** - [ X] This request is **not a support request or question**, both of which are better suited for either the [discussions section](https://github.com/qbittorrent/qBittorrent/discussions), [forum](https://qbforums.shiki.hu/), or [subreddit](https://www.reddit.com/r/qBittorrent/). The [wiki](https://github.com/qbittorrent/qBittorrent/wiki) did not contain a suitable solution either ## Description <!-- ################################## IMPORTANT ################################## Delete each "(type here)" indicator and type your text in their place in the subsections below. You MUST fill in ALL subsections marked with "(type here)" with the appropriate information. Please make sure the description is worded well enough to be understood. Provide a detailed description of the feature and as much context and examples as necessary. If the feature request has to do with visual elements and the GUI, images/screenshots are always helpful. For more information consult the Contributing Guidelines at https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md. Use the Preview tab before posting to make sure your report looks like it is formatted properly. You don't need to delete these comments, they won't show up in the final post. --> ### Suggestion I have noticed that on popular torrents I sometimes download off of peers/seeds that upload at below KiB/s speeds. These peers/seeds in essence do not contribute to my downloading of the torrent, in fact they are hogging slots for other, faster peers/seeds to occupy. I would suggest to have a minimal peer/seed upload speed (adjustable) option implemented so those peers/seeds can be discarded if they fail to reach the limit. By discarded I mean stripped from the ability to upload to you, but in the case of peers of course still allowed to download off of you. This feature could be implemented on a global basis (global limit) but would be enforced on a per torrent basis. So if the peer/seed appears on another torrent with higher speeds, it doesn't get affected for that particular torrent. I would argue that this enhances the distribution of the torrent (faster downloading allows for faster seeding when done) without being in danger of being labeled as a leech as you do not limit uploads, just downloads. Makes sense? ### Use case all torrent downloads with qBittorrent ### Extra info/examples/attachments ![Screenshot104132](https://user-images.githubusercontent.com/2780450/128462896-40f3b702-4ed9-42c1-8a6d-ca65eacec0eb.png)
deekerman 2026-02-21 22:36:10 -05:00
Author
Owner

@thalieht commented on GitHub (Aug 6, 2021):

Duplicate of #13247 #7614 #4755 #4490

Note to other bug handlers: as history has shown, if you lock an issue too fast then OP will simply make a new one instead of saying what they have to say here, so i suggest to wait a few days before locking.
I'd close it but you guys might lose track of it since you insist on locking everything :)

@thalieht commented on GitHub (Aug 6, 2021): Duplicate of #13247 #7614 #4755 #4490 Note to other bug handlers: as history has shown, if you lock an issue too fast then OP will simply make a new one instead of saying what they have to say here, so i suggest to wait a few days before locking. I'd close it but you guys might lose track of it since you insist on locking everything :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#12326
No description provided.