mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Optional minimum peer/seed upload speed #12326
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#12326
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheSparrowLenz on GitHub (Aug 6, 2021).
Feature request
Checklist
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
@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 :)