Repository navigation
Dynamic Speed Limit on Specified Trackers #1143
Replies: 2 comments
Agent BriefCategory: enhancement Current behavior: Desired behavior: The report also asks for a ceiling shared across everything a rule matches (500 Mbps total), and beyond that a tracker priority that hands spare bandwidth down a ranked list. qBittorrent exposes no per-tracker bandwidth pool, so qui would have to divide a budget across the matched torrents and rewrite their individual limits continuously: a control loop at seconds granularity, not the current interval-based evaluation. Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: The shared ceiling and the tracker-priority variant are a bandwidth control loop rather than a new condition field, so the size and the architecture are a maintainer call. Building only the instance-rate condition would cover the trigger the report describes but not the "total across a tracker" part of it. |
|
A use case I have for this is or something similar I have an instance with 13k torrents and multi gigabit internet. I have to limit my qbit speed otherwise I would be uploading TBs every day. I've recently joined a new site where its a new content type, so I don't really have anything to cross-seed. The ability to exclude this tracker from my speed limit would be useful to help build up my buffer on this new site. |
Uh oh!
There was an error while loading. Please reload this page.
Set speed limits on specified trackers depending on the overall bandwidth being used by qBittorrent. For example, if overall upload speed exceeds 900Mbps for 30 secs, limit hungry cross-seeded trackers to 500Mbps total so that primary trackers get some breathing room.
An even better alternative would be tracker priority, giving primary trackers access to as much bandwidth as they need and then allowing others to use the balance, but that doesn't feel possible.
All reactions