qbit_manage icon indicating copy to clipboard operation
qbit_manage copied to clipboard

[FR]: please add option to prevent disabling of upload speed limits when last_active is triggered

Open kilinrax opened this issue 8 months ago • 2 comments

Is your feature request related to a problem? Please elaborate.

My broad goal is for certain 'low priority' trackers to have a shared limit, which is always active for every torrent on that tracker. And also, to delete the least popular well seeded torrents automatically to save disk usage.

I want to not delete torrents which will continue to accrue upload credit, or where I am one of the last few seeders. The app seems to be intended to only do the opposite of that; i.e. delete the most popular (high ratio) torrents first, and the least popular (low ratio) torrents last.

My intended "workaround" is to set:

    max_seeding_time: 2mo
    last_active: 30d
    min_num_seeds: 3
    limit_upload_speed: 2000
    enable_group_upload_speed: true

... which I thought would delete files at least 2 months old, with 3+ seeds and no activity in the last month. However, any activity also disables the upload limits.

There are basically no circumstances where I want upload limits disabled, as it effectively means any upload limit is only 'active' when the torrent is inactive.

In general there doesn't seem to be an intuitive way, if there is one, to configure a tracker to only keep popular torrents, not unpopular ones.

Describe the solution you'd like

A boolean option to make last_active only affect cleanup, not upload limits.

Does your solution involve any of the following?

  • [x] New config option
  • [ ] New command option

Describe alternatives you've considered

I've considered whether it's possible to use multiple prioritized share_limits blocks and tags to achieve the behavior I want, using the config options which currently exist. If it's possible, I can't work out how to do it.

Who will this benefit?

Anyone who wants to cross seed across both low priority and high priority trackers, and wants to keep most of their upload bandwidth free for the high priority trackers.

Additional Information

No response

kilinrax avatar Apr 24 '25 10:04 kilinrax

Added in e2dc031 , please set reset_upload_speed_on_unmet_minimums to False and test in develop branch

bobokun avatar Jul 18 '25 20:07 bobokun