Deluge Forum

"Don't resave fast-resume for seeding torrents"

Every time i restart my client it goes through a full recheck, which takes absolutely ages. Why were we not given the choice to turn this on or off?

sluthead wrote:"Don't resave fast-resume for seeding torrents"

Every time i restart my client it goes through a full recheck, which takes absolutely ages. Why were we not given the choice to turn this on or off?

Because fast-resume files are saved when a torrent goes into a seeding/finished state. So by re-saving fastresume files for seeding torrents (during the 1-minute fast-resume saving timer) is pointless and degrades performance.

So what to do? This is really annoying. It takes HOURS!!

andar wrote:

sluthead wrote:"Don't resave fast-resume for seeding torrents"

Every time i restart my client it goes through a full recheck, which takes absolutely ages. Why were we not given the choice to turn this on or off?

Because fast-resume files are saved when a torrent goes into a seeding/finished state. So by re-saving fastresume files for seeding torrents (during the 1-minute fast-resume saving timer) is pointless and degrades performance.

huh? more pointless than sitting for 20 minutes not being able to download or seed anything because it wants to check each torrent individually. Funny way at spinning "degrading performance"

sluthead wrote:

andar wrote:

sluthead wrote:"Don't resave fast-resume for seeding torrents"

Every time i restart my client it goes through a full recheck, which takes absolutely ages. Why were we not given the choice to turn this on or off?

Because fast-resume files are saved when a torrent goes into a seeding/finished state. So by re-saving fastresume files for seeding torrents (during the 1-minute fast-resume saving timer) is pointless and degrades performance.

huh? more pointless than sitting for 20 minutes not being able to download or seed anything because it wants to check each torrent individually. Funny way at spinning "degrading performance"

That shouldn't happen if you shutdown deluge properly. The idea of resaving a fastresume file that has already been saved is redundant.

As you can see this happens - even when shut down properly. I even have to close it manually before shutting down Windows, because Deluge itself as well as the .torrent files and downloads are located on a truecrypt volume. If anything is left opened it will delay or stop the process...

Bzzz wrote:As you can see this happens - even when shut down properly. I even have to close it manually before shutting down Windows, because Deluge itself as well as the .torrent files and downloads are located on a truecrypt volume. If anything is left opened it will delay or stop the process...

Then this is a bug unrelated to the change mentioned.

Yeah it's a bug then because it is happening even when shut down properly.

I just assumed that because it seemed to appear in the changelog that this was a feature

sluthead wrote:Yeah it's a bug then because it is happening even when shut down properly.

I just assumed that because it seemed to appear in the changelog that this was a feature

it doesnt appear on the changelog. "RESAVING" is not the same thing as "saving". that's why they're different words

i have the same problem as sluthead, running deluge 0.5.8.4 on ubuntu 7.10 i386. it's really annoying!