The way I figure it, disk overload always appear at the start of a download. Utorrent doesn't create the file(s) unless enough data is gathered. So, in my case, the download starts at 0 kb and skyrockets to 6Mb in about 4 seconds. By that time the disk goes into an overload state because it first creates the files and then move the data into them.It'll slow speeds to a trickle until the disk ceases to be overloaded
Pre-allocating the data makes sense: You create the container first and then move the data in it.
However, using the disk cache settings overrides the automatic cache size. Instead of moving 30Mb you set it to move 500mb. Doing so, utorrent will write to the disk less by carrying high amount of data at one time. But it takes away RAM and it doesn't guarantee that disk overload won't be produced.
I think writing to the disk every 8 seconds is as bad as disabling disk cache. Reason is that some times the HDDs park their head and constantly using it may wear out the drive.
Bookmarks