#2059: Deluge not agressive enough during initial (first) tracker update routine
------------------------------------------------------------+---------------
Reporter: AlderaaN | Owner:
Type: feature-request | Status: new
Priority: major | Milestone:
1.4.0
Component: core | Version:
Keywords: tracker, update, aggressive, timeout, time-out |
------------------------------------------------------------+---------------
Changes (by Cas):
* component: libtorrent => core
* milestone: => 1.4.0
Comment:
This change has been added to libtorrent trunk so this will not be in the
Deluge 1.3 however it can be added to the development branch.
From the libtorrent docs:
''tracker_backoff'' determines how aggressively to back off from
retrying failing trackers. This value determines x in the following
formula, determining the number of seconds to wait until the next retry:
delay = 5 + 5 * x / 100 * fails^2
It defaults to 250.
This setting may be useful to make libtorrent more or less aggressive
in hitting trackers.
Python binding for tracker_backoff is in session_settings.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2059#comment:4>
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.
