#1511: Swarm Health Based Queue Management
-----------------------------+----------------------------------------------
Reporter: WillyWolly | Owner:
Type: feature-request | Status: new
Priority: major | Milestone: 1.3.x
Component: other | Version: other (please specify)
Keywords: |
-----------------------------+----------------------------------------------
Deluge currently determines its 'seed rank' solely based on seed time and
ratio, as per the FAQ.
However, in most situations it is beneficial to start only those torrents
that are needed most for the '''swarm''', depending on the number of
seeders and peers available. A torrent may be very well seeded, but Deluge
still needs to keep it active until it has fulfilled its time and ratio
requirements. It's better to stop such popular torrents and use upload
bandwidth for older torrents that don't have as much seeds.
Also other functionality is required for a modern client, such as
automatically starting torrents with 0 peers, so that unpopular torrents
would still register seeds at the tracker, for potential downloaders. And
there are even more options such as exceptions and such for adhering to
tracker requirements.
Please look at Vuze's (Azureus) queue management implementation which is
perfect. (But I understand it's hard to do it right.)
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/1511>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
