Frequent tracker timeouts
Posted: Mon Jun 14, 2010 8:08 pm
Hi!
I've recently switched from Azureus/Vuze to Deluge, and *wow*, the difference in memory usage is astronomical!. I'm gradually restarting the torrents I was previously seeding, but now I've run into a problem: lots of torrents time out (Tracker status on the Status tab says "<trackername>: Error: Connection timed out").
When I was still using Azureus, I frequently had been seeding over 350 torrents accross several trackers without a hitch (not counting the memory usage) and the webpages of the trackers always showed I was seeding that number of torrents.
While using Deluge, I'm now seeding 98 torrents ("Auto Managed" off) but only around 20 from different trackers stay active (and as such are listed on the trackers' websites) - the rest keeps timing out. The ones that are running cycle with torrents that were previously timed out and vice versa. I've tried fiddling with the different numbers of connections on the Bandwidth preferences page, but using high (800) or low numbers (50) and several steps in between doesn't seem to matter. The number of actual reported connections rarely go above 100. I've also tried debug logging, but that only shows no errors.
Does anyone have a clue how to keep these torrents from timing out? Because I don't.
I'm running Deluge v1.2.3 GTK (tried both classic and non-classic mode) (libtorrent 0.14.10.0), which I installed from the Fedora F13 x86_64 updates-testing repo, and am using the Blocklist-plugin. Checking my incoming port status results in a nice green dot.
PS. Does Deluge/libtorrent support batch/grouped scraping (like Azureus/Vuze)?
I've recently switched from Azureus/Vuze to Deluge, and *wow*, the difference in memory usage is astronomical!. I'm gradually restarting the torrents I was previously seeding, but now I've run into a problem: lots of torrents time out (Tracker status on the Status tab says "<trackername>: Error: Connection timed out").
When I was still using Azureus, I frequently had been seeding over 350 torrents accross several trackers without a hitch (not counting the memory usage) and the webpages of the trackers always showed I was seeding that number of torrents.
While using Deluge, I'm now seeding 98 torrents ("Auto Managed" off) but only around 20 from different trackers stay active (and as such are listed on the trackers' websites) - the rest keeps timing out. The ones that are running cycle with torrents that were previously timed out and vice versa. I've tried fiddling with the different numbers of connections on the Bandwidth preferences page, but using high (800) or low numbers (50) and several steps in between doesn't seem to matter. The number of actual reported connections rarely go above 100. I've also tried debug logging, but that only shows no errors.
Does anyone have a clue how to keep these torrents from timing out? Because I don't.
I'm running Deluge v1.2.3 GTK (tried both classic and non-classic mode) (libtorrent 0.14.10.0), which I installed from the Fedora F13 x86_64 updates-testing repo, and am using the Blocklist-plugin. Checking my incoming port status results in a nice green dot.
PS. Does Deluge/libtorrent support batch/grouped scraping (like Azureus/Vuze)?