Opened 11 years ago

Closed 11 years ago

Last modified 9 years ago

#4229 closed Enhancement (wontfix)

Limit torrent based on seeder:leecher ratio

Reported by: Harry Owned by:
Priority: Lowest Milestone: None Set
Component: Transmission Version: 2.22
Severity: Trivial Keywords:
Cc: transmission@…


Suggestion: transmission should have an option (default off) to prefer seeding torrents that have a lower seeder:leecher ratio.

Reasoning: With 700+ torrents and only 50 KB/s uplink to spare, under-seeded torrents are not preferred. Transmission should have an option to prefer to send your bits to a torrent with 1:100 seeder:leecher ratio, rather than a 100:1 seeder:leecher ratio torrent.

Uses: Transmission users with many torrents will have an option to seed the underseeded torrents - this will allow for longer longevity and generally improve the swarm's health.

Change History (3)

comment:1 Changed 11 years ago by livings124

In most cases, users simply want to seed as much as possible. I think letting the app decide, as it does now, is the best option. This way, it can ensure the total upload is highest. I honestly don't see this feature being appealing to most, as opposed to the existing priority option.

comment:2 Changed 11 years ago by livings124

  • Resolution set to wontfix
  • Status changed from new to closed

comment:3 Changed 9 years ago by slaute

I sum up my voice to this feature request.

This would help keeping the minority swarms' health up, which in my opinion is one of the weak points of the bittorrent system.

The feature should not reduce the total upload, which should be always kept to the maximum set up by the user. However, if for example seeding two torrents, one with more seeders than the other, the priority should be given to the torrent with less seeders. Another type of implementation could be disabling or enabling torrents based on the number of seeders available, which I see certainly easier to implement. A checkbox could enable this feature on a torrent basis.

I have no idea of how Transmission internally manages priorities, but there could be an additional priority setting like "auto", based on seeders number.

I insist that in any case the maximum upload set up should always be guaranteed, ensuring livings124's point that I share and consider important.

I've already seen this feature in the former Azureus many years ago before it became Vuze.

Note: See TracTickets for help on using tickets.