![]() ![]() 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. I've done clean installs, upgrades, clean uninstalls and re-installs and nothing makes a difference. This is because uTorrent 2.2.1 begins downloading the next torrent, then caches the data in RAM, rather than writing it to the local disk. There is something seriously wrong with 3.0. Note that if your download temp folder is on a local drive and then uTorrent auto-moves to a GigE network drive, you can run into the Disk Overloaded 100 issue when the torrent is over like 4GB. 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. ![]() It has been actually the ONLY issue I have had with utorrent. ![]() I get the disk overloaded problem constantly under 3.0. Not a single issue since that ' disk overloaded 100 '. This problem has rendered version 3.0 useless for me. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |