Ticket #2059 (assigned feature-request)
Add support for libtorrent tracker_backoff option
|Reported by:||AlderaaN||Owned by:|
|Keywords:||tracker, update, aggressive, timeout, time-out||Cc:||pcfregister@…|
I use autodl-irssi to match the latest releases in my tracker.
Here's what happens: 1. My autodl is set to pass on .torrent files after 35 seconds to Deluge's watch-dir.
2. Deluge picks up the .torrent.
3. Deluge tries to update for the tracker once.
4. If the uploader of said torrent didn't perform "update tracker" on his client in a timely manner - Deluge will time-out and set itself to retry once more in no less than 30 minutes!
5. Those first 30 minutes, in SeedBox?-heavy private trackers, could mean you either:
5. A. Scored big: if Deluge managed to sync up with the tracker and you caught the swarm early.
5. B. Failed miserably: if Deluge timed-out for 30 minutes on the first announcement, and you managed to destroy your ratio on a particular torrent.
This is something that doesn't happen in rTorrent/ruTorrent - where it seems to keep on auto-retrying in very small intervals until it's able to sync up with the tracker.
And so, I kindly ask you implement a more aggressive initial tracker-updating mechanism, just until Deluge is able to pick up and sync with the tracker.
Something in the range of every 5 seconds would be very good. Again, just until it syncs up with the tracker.
BTW: increasing the upload-delay-secs = to anything higher than 35 seconds i quite futile, since there could always be those odd torrents where even after 90 seconds they'd still won't sync, and after 150-180 seconds they would..