Jump to content

Checking after crash


Icecubes

Recommended Posts

I can accept the odd crash, but is there anyway to stop it from re-checking the last successful 20 downloads when I start it up again.  I have large torrents and after a crash it spends about 30 mins rechecking the last 20 downloads.  When it crashed 17 of them were complete and seeding, only 3 were actively downloading.  I can appreciate those 3 need to be checked but why the other 17 that were fine and complete?

 

The crash occurred because of using all the buffer memory - some windows cannot assign memory message - this is on a 16GB machine with masses of free ram....

 

/Icecubes

Link to comment
Share on other sites

without raising the cache settings it crashes anyway with 100% disk overload plus I get crap speeds.  With the cache enabled to a large amount I get fantastic speeds, so that situation is actually about choosing the lesser of two evils anyway as both result in a crash or hang, and as said I don't mind the odd crash... So back to the actual question....

 

Is there anyway to stop it re-checking torrents that are downloaded and complete because that is simply a waste of time and disk io.. they are complete, marked as complete and seeding, why do they need to be checked?

Link to comment
Share on other sites

maybe you have a suggestion?  As mentioned the defaults leave me with 100%disk overload and it hangs, and the increased settings I have now where I assign a gig of ram give me great speed and for the most part work fine, until i have multiple torrents open.  then I get the cannot assign memory messages - even though memory is available - and cause the crash according to you.

 

What would you suggest would be optimal values?  I have a 500mbit line, 16GB ram with plenty spare and a dedicated 1TB drive on a 6GB/s Sata controller

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...