Again this assumes you have a pretty average & modern 1TB or larger hard drive. But when we increase the cache to 1GB we are able to sustain full speed downloads for an hour or more. The Hard Drive here is writing out the information as fast as possible but it cannot keep up because the randomness of the incoming files is simply to high. Now as seen in the above image having a small 32MB cache is easily filled within a few minutes. Remember, if the cache becomes full and your hard drive cannot keep up with the pace of incoming file pieces your downloads will slow to a crawl or stop entirely.
I've created the following image to show you how having this large cache makes an impact on your downloads. Perhaps 512 or 1024 (512MB & 1GB respectively). Rented servers start at 100Mb you will probably want to set this value So if for example you have a 50Mb or 100Mb internet line which areīecoming common in the western world and most seedboxes and cheap Is, will be the speed you will be downloading at. Guide we assume that whatever the maximum speed of your internet line The speed of your internet and the speed of your hard drive. Now changing this setting to a high number depends on two main things. you will see a tick box that says 'Override automatic cache size' and Source: Comment in Reddit /r/torrents post, 'uTorrent Trouble: "Disk Overload 100%"', by user, lolibattlemech I've reverted back to 2.2.1 for the time being since this is my primary media server and having it freeze up is not an option.Set uTorrent to be like this in Preferences » Advanced » Disk Cache: I've done clean installs, upgrades, clean uninstalls and re-installs and nothing makes a difference. There is something seriously wrong with 3.0. Seeing as the disks in questions is an 8TB array with dual controllers (and at least 4 TB free at the moment) I doubt seriously it is the hardware-especially since the older version works fine. I tried 3.0, 254460 this morning and it locked up the system hard after less than 15 minutes of running with the exact same set of torrents, same hardware, same OS (win2003 server). I just ran 30 days under 2.2.1 and experienced no issues. Same torrents, same hardware, same settings under 2.2.1 and no problems. Within 10 minutes of launching 3.0 the hardware interrupts (from proc explorer) skyrocket from an average of < 2 to over 30 when utorrent 3.0 runs, disk overloaded messages appear and the system becomes nearly unusable as CPU is pegged. I get the disk overloaded problem constantly under 3.0. This problem has rendered version 3.0 useless for me.
0 kommentar(er)
