Part of the process has been to capture the magnet links of torrents currently managed by the previous client, and then to add them to Deluge.
The torrents successfully populate the Deluge instance, but communication with trackers has presented as problematic. Whereas the previous client has been able to discover peers and seeders with the general success, Deluge has had extremely limited success.
From observation and reading, I have formed some rough ideas of the differences between the operation of the two applications. These ideas may be inaccurate, and I would welcome elaboration where helpful and correction where necessary.
According to my extrapolation, Deluge operates according to the following rules, which may be different from other clients:
- Deluge only uses one tracker per torrent at a time.
- If contact with a tracker is unsuccessful, or if the tracker offers no peers for some torrent, then Deluge simply repeats an announcement attempt to the same tracker at a later time, without trying other trackers.
- Even if a tracker provides peers, other trackers may be tracking other peers or a higher total count of peers, which Deluge will never discover due to preference for only communicating with one tracker. (From the other client, which maintains and displays peer lists from all trackers at the same time, it is apparent that trackers vary widely with respect to total number of peers available for a particular torrent.)
Thus, running side by side, the two clients perform very differently, with the results from deluge being the less favorable. The aggregate effect is that most torrents added to Deluge at this time are not downloaded or seeded, due to inability to discover peers.
I would appreciate any comments helping me to understand the method Deluge uses for contacting trackers, and how find a way to download and seed torrents successfully.