#2059: Deluge not agressive enough during initial (first) tracker update routine
------------------------------------------------------------+---------------
 Reporter:  AlderaaN                                        |       Owner:      
 
     Type:  feature-request                                 |      Status:  new 
 
 Priority:  major                                           |   Milestone:  
1.3.x
Component:  other                                           |     Version:  
1.3.4
 Keywords:  tracker, update, aggressive, timeout, time-out  |  
------------------------------------------------------------+---------------
 Greetings.

 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..


 Specs:
 Deluge Client: v1.3.4
 Deluge Server: v1.3.4
 libtorrent: v0.15.10.0
 OS: Linux version 2.6.39.2-grsec-xxx-r1.5.1 ([email protected]) (gcc
 version 4.4.3 (Gentoo 4.4.3-r2 p1.2) ) #1 SMP Wed Jun 29 00:47:56
  EDT 2011

-- 
Ticket URL: <http://dev.deluge-torrent.org/ticket/2059>
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.

Reply via email to