M: Using qbittorrent, my downloading is fine, but nothing that I have set for seeding uploads unless I have forced it to run. I have a feeling I set the settings to the wrong numbers. It is throttle for practical purposes; it currently can download at 3Mb and upload at 1. Where should I be looking in terms of behavior, connections, and speed? Or should I be looking in different preferences? I don’t want to be a leech, but my equipment is old enough that I don’t want to stress it out, so I would prefer not to haveany single file uploading at more than 100 K, but I’m not sure how to get it to do that without completely throwing open all the resources in a way that, given the age of my equipment, could cause regular overloads.
G: To balance seeding in qBittorrent without overloading your old hardware, you’ll want to tweak Speed, BitTorrent, and Queueing settings carefully.
Go to: Tools > Options >
Speed
100 KiB/s3000 KiB/s or 0 (unlimited)If you want a “day mode / night mode” (e.g. no upload during the day):
0
upload during 9am–5pm)Go to: Options > BitTorrent
uTP, DHT, PEX, and
Local Peer DiscoveryGo to: Options > Queueing
Older systems often stall if:
If the above tweaks still cause sluggishness, reduce:
Let me know your specs if you'd like help with buffer/cache settings to reduce disk stress.
M: Is there anyway in the program to accomplish the following: If the torrent has not had any activity in the last 15 minutes, move it to the bottom of the queue and let the next torrent try running? I end up with massive sets of torrents, which look like good ideas, but which Are rarely seeded, or only seeded at night, from the internet archive. With limited resources – and even with a bleeding edge set up, after a certain point all resources would eventually be limited – I can’t just try starting all of them.
G: qBittorrent does not have built-in support for dynamic seeding prioritization based on recent activity, like “no activity in 15 minutes → move to bottom of queue.” But here’s what can be done, along with some practical workarounds and semi-automated options.
Options > Queueing → ✅ Do not count slow torrents
This lets new torrents get a chance to activate even if the max upload slots are full, as long as some of those uploads are slow (idle or near-idle).
🔹 Definition of "slow":
qBittorrent uses an internal threshold (usually <1 KiB/s for several
minutes). It’s not exactly 15 minutes, but it helps bypass
frozen uploads.
Set:
The slow ones will gradually drop out if they get no activity, letting others try.
If you're willing to script, you can use the qBittorrent Web API to:
You’d use something like:
GET /api/v2/torrents/info?filter=seedingupspeed or last upload timePOST /api/v2/torrents/pausePOST /api/v2/torrents/resumeThis would act like a “rolling seeder test.”
Want a starter script in Python or shell?
If you don’t want full automation, but can run a script daily or weekly, a lighter solution:
It’s still semi-manual, but scalable with batch tools.
| Goal | Best Option Available |
|---|---|
| Automatic queue demotion | ❌ Not built-in |
| Prioritize active uploads | ✅ Use "Do not count slow torrents" |
| Avoid resource overload | ✅ Tune queueing + upload limits |
| Dynamic testing of idle torrents | 🛠️ Write a script using Web API |
Let me know if you want a minimal script that cycles seeding torrents based on activity.