Why does Deluge stop seeding all torrents when "Checking" a file?
Posted: Wed Apr 05, 2017 2:42 pm
This is with 1.3.14 on Windows 7
Pretty much what the titles says.
I can be seeding out any number of torrents and as soon as I add a new one to seed and Deluge has to "check" the files before it begins seeding, all my other torrents rapidly begin to drop bandwidth until they are are almost zero. Right now my cumulative 1.1 MB/s between 4 torrents was reduced to about 10kbps - so essentially 0.
Since checking a large torrent can take 30 minutes or more, and I sometimes add several a day, this causes me to lose valuable seeding time.
I see no good reason why the program should do this. The only reason I can think is to regulate disk I/O. But - if that's the case, why doesn't it also do this when creating a new torrent file (Ctrl+N)? Also, the program can't account for I/O from non-deluge sources, so it seems silly to throttle it.
I'd like to think this was a bug - but I can't find anything else discussing it.
thanks
Pretty much what the titles says.
I can be seeding out any number of torrents and as soon as I add a new one to seed and Deluge has to "check" the files before it begins seeding, all my other torrents rapidly begin to drop bandwidth until they are are almost zero. Right now my cumulative 1.1 MB/s between 4 torrents was reduced to about 10kbps - so essentially 0.
Since checking a large torrent can take 30 minutes or more, and I sometimes add several a day, this causes me to lose valuable seeding time.
I see no good reason why the program should do this. The only reason I can think is to regulate disk I/O. But - if that's the case, why doesn't it also do this when creating a new torrent file (Ctrl+N)? Also, the program can't account for I/O from non-deluge sources, so it seems silly to throttle it.
I'd like to think this was a bug - but I can't find anything else discussing it.
thanks