starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Settings - BitTorrent- add limit by number of seeds #9607

New issue

Open

opened 2026-02-21 20:16:50 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 20:16:50 -05:00

Owner

Originally created by @Furnicarium on GitHub (Jan 5, 2020).

4.2.1
no problems, just a wish. I like to seed only rare torrents where I am the only seeder.

Originally created by @Furnicarium on GitHub (Jan 5, 2020). 4.2.1 no problems, just a wish. I like to seed only rare torrents where I am the only seeder.

deekerman added the

Feature request

label

2026-02-21 20:16:50 -05:00

deekerman commented

2026-02-21 20:16:52 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jan 5, 2020):

A seeding torrent does not know how many others are also seeding the same torrent, as seeds do not connect to each other...except rarely, and then only very briefly.

Trackers, PEX, LSD/LPD, and DHT miscount seeds -- often considerably over-estimating the number of seeds still running the torrent.
A peer that finishes the torrent and stops it immediately is often reported as an available seed to new peers for hours to days after it left.

@Seeker2 commented on GitHub (Jan 5, 2020): A seeding torrent does not know how many others are also seeding the same torrent, as seeds do not connect to each other...except rarely, and then only very briefly. Trackers, PEX, LSD/LPD, and DHT miscount seeds -- often considerably over-estimating the number of seeds still running the torrent. A peer that finishes the torrent and stops it immediately is often reported as an available seed to new peers for hours to days after it left.

deekerman commented

2026-02-21 20:16:55 -05:00

Author

Owner

@Furnicarium commented on GitHub (Jan 5, 2020):

Ok, I understand. thank you.

@Furnicarium commented on GitHub (Jan 5, 2020): Ok, I understand. thank you.

deekerman commented

2026-02-21 20:16:55 -05:00

Author

Owner

@a-raccoon commented on GitHub (Jan 9, 2020):

@Seeker2 I don't think any of that necessarily invalidates the request, though. For instance, a checkbox "[x] Always seed at-risk torrents with N or fewer seeds." could work in tandem with the other seed_until ratio or time settings. Having this checkbox selected would prevent the torrent from being paused and dropping out of the seed queue. The estimate would be pulled from the tracker, and the default N threshold could be set to 2 or 3.

Another option I'd suggest adding is "[x] Prioritize seeding at-risk and unhealthy torrents." In addition to the above, this would put effort into seeding torrents that have a particularly high "leech" to "seed" ratio, and especially torrents that register 3 or more peers all stuck at the same % complete, as you may be their only hope of ever completing that torrent.

I do all this by hand currently, and it takes a lot of manual maintenance I wish were automated.

@a-raccoon commented on GitHub (Jan 9, 2020): @Seeker2 I don't think any of that necessarily invalidates the request, though. For instance, a checkbox "[x] Always seed at-risk torrents with N or fewer seeds." could work in tandem with the other seed_until ratio or time settings. Having this checkbox selected would prevent the torrent from being paused and dropping out of the seed queue. The estimate would be pulled from the tracker, and the default N threshold could be set to 2 or 3. Another option I'd suggest adding is "[x] Prioritize seeding at-risk and unhealthy torrents." In addition to the above, this would put effort into seeding torrents that have a particularly high "leech" to "seed" ratio, and especially torrents that register 3 or more peers all stuck at the same % complete, as you may be their only hope of ever completing that torrent. I do all this by hand currently, and it takes a lot of manual maintenance I wish were automated.

deekerman commented

2026-02-21 20:16:55 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jan 9, 2020):

Yes, it doesn't invalidate the request...such a feature would only be partially successful due to the problem I mentioned with counting active seeds and peers.

Another problem currently is qBitTorrent's torrent queuing system is buggy almost to the point of unusable when trying to keep only a few torrents active with 100+ torrents queued.

@Seeker2 commented on GitHub (Jan 9, 2020): Yes, it doesn't invalidate the request...such a feature would only be partially successful due to the problem I mentioned with counting active seeds and peers. Another problem currently is qBitTorrent's torrent queuing system is buggy almost to the point of unusable when trying to keep only a few torrents active with 100+ torrents queued.

deekerman commented

2026-02-21 20:16:55 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**

deekerman referenced this issue

2026-02-21 20:41:33 -05:00

[Tool] Batch close old issues #10312