mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Can't limit the number of active uploads while keeping all torrents seeding #9994
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#9994
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 @j03bj03 on GitHub (Mar 27, 2020).
qBittorrent version and Operating System
qBittorrent 4.2.1 64-bit
Windows 7 Ultimate
What is the problem
This has been an ongoing issue for me for a very long time. I am seeding many torrents, like many, many, many. What I want to do is limit the number of simultaneous active uploads to prevent qBittorrent from crashing, while keeping ALL my torrents seeding at the same time. I mean, I want all the torrents to be available, but just not have too many of them upload at the same time.
What is the expected behavior
In Tools>Options>BitTorrent, I set Maximum active torrents to -1 to keep all torrents seeding. I also set Maximum active uploads to the maximum number of active uploads I would like at the same time. This should make all my torrents available and seeding (active torrents), but prevent too many of them from starting uploading at the same time. However, regardless of which combination of these options I try, there is absolutely no way I am able to limit the number of uploading torrents AND keep all seeding at the same time. If I set Maximum active torrents to something else than -1, of course, I am able to limit my active uploads, but doing this puts most of my torrents in "queued" status, which I don't want. Let's say I have 2000 torrents, if I set Maximum active torrents to 20, then 1980 become "queued", which is totally ridiculous, because then I stop uploading at all, because it's like qBittorrent just doesn't understand which ones it needs to seed and just randomly picks up 20 torrents among the 2000, most likely not picking up torrents that need seeding. What I want is to have ALL torrents seeding, but when the demand gets too high, that qBittorrent limits the number of active uploads. Logically, this should be achieved by setting Maximum active torrents to -1 and setting Maximum active uploads to whatever I believe is the maximum capacity for my computer setup.
Also, as a side note, if I put Maximum active torrents to -1 and Maximum active uploads to, for example, 10, and then I reset qBittorrent... Then, ALL my torrents except 10 are on "queued" status... It's like if both the "Maximum active torrents" and "Maximum active uploads" switches were doing the exact same thing. That doesn't make any sense...
@ghost commented on GitHub (Mar 28, 2020):
Set a limit in upload slots in connection settings or wait for a future release with improved rate based choker.
@Seeker2 commented on GitHub (Mar 28, 2020):
If you have enough activity spread across many torrents to easily max out your upload speed limit, you may want to limit the number of upload slots PER torrent very low -- like only 1-4. Likewise, max connections per torrent should probably not be higher than 5-10 when set like this.
This way, 1 really busy torrent doesn't "grab" 20+ upload slots because it has that many connected peers...and probably get >90% of all your upload speed. (...causing other torrents with peers to mostly "starve".)
@j03bj03 commented on GitHub (Mar 28, 2020):
Hello! Thanks for answers!
There are never that many peers leeching at the same time on this tracker, and it is really rare that more than 2 are connected on the same torrent at the same time, because I am mainly seeding old torrents for diversity. The problem is only during peak hours, when I go above ~30 torrents uploading. My connection is fiber optic 1GBPs, so sometimes it just fries my computer when there's too many people.
So, your suggestions make sense. I rarely play with "max slots" options, but I tried it out. I put max connections per torrent to 3, max upload slots per torrent to 2, and global max upload slots to 30. I'll see if that changes anything and report back once I did a bit of testing.
Thanks :)
@j03bj03 commented on GitHub (Apr 4, 2020):
Hi again,
So, I did some testing with your suggestions and I was (finally) able to limit the number of active uploads while keeping all my torrents available for seeding at the same time. However, I found another bug which is almost the same bug as I reported in my original post.
At first, I had set "Global maximum number of connections" to 100 and "Global maximum number of upload slots" to 30, thinking qBittorrent would limit my number of active uploads to 30. However, a few hours later, first thing I noticed is that I had 49 torrents uploading and soon after qBittorrent crashed.
Then, I set both "Global maximum number of connections" and "Global maximum number of upload slots" to 30, and only then did qBittorrent start limiting my uploading torrents to 30 slots total. I did a little bit more testing, and I could confirm this behavior.
So, my conclusion is that the "Global maximum number of upload slots" option has no effect at all. To effectively limit the number of upload slots, you need to use the "Global maximum number of connections". It's the only way it worked for me. (BUG #1)
Another conclusion was in my original post, that both the "Maximum active torrents" and "Maximum active uploads" options do the exact same thing. (BUG #2)
I am now able to do "almost" what I wanted, but I don't know if I should close this thread, because it still contains 2 bugs on which someone might want to work in the future.
@FranciscoPombal commented on GitHub (Apr 4, 2020):
@j03bj03 thank you for the report and investigation.
My recommendation would be to open 2 separate issue reports, one for each bug you found, so that they can be individually tracked more effectively, rather than just being mentioned in a comment of another issue. As for this one, I assume it can be closed?
@j03bj03 commented on GitHub (Apr 5, 2020):
@FranciscoPombal
I will follow your advice and open 2 reports. I will also close this one. Thank you!