mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Terrible upload speed if download is set slow #1135
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#1135
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 @SandyMangina on GitHub (Jan 30, 2014).
My bandwidth cap is pretty restrictive but allows for unlimited downloading between 2-8am. I load the torrents in the client during the day with the global rate limit for downloads set to 1kb/s (zero value gives unlimited) and then set the alternative rate limits to unlimited between 2-8am to download the torrents during the off-peak hours. Unfortunately I've noticed that when my download speed is set low, my uploads are capped pretty heavily. Clicking the alternative rate limit button instantly relives the cap and maxes out my upload speed.
Any suggestions?
@sledgehammer999 commented on GitHub (Jan 31, 2014):
This is how the bittorrent protocol works. Even when you upload ONLY, you need to also receive data. These data are protocol/network related. eg acknowledgment that you have received piece X that the other client just sent you, communication between other peers, between DHT nodes, between trackers. All these want some downlink bandwidth available. So if you have a really limited downlink and a lot of messages to receive then it throttles down the uplink too. But I don't think you need a LOT of downlink to operate at max uplink. (depends on how big your uplink is). Try incrementing your downlink by 1KB/s per time. I think you'll be ok around 5-10KB/s.