[µTorrent 3.1.2 stable (26821)]

... but my feeds showed only previously downloaded torrents, and would not show new feed data. ....

Same for me

[µTorrent 3.1.2 stable (26821)]

Disk Overload 100% issue in Win2k3 still exists. Is it going to be fixed someday?

Yes' date=' someday... Are you going to upgrade from Win2k3 someday? ... [/quote']

Lulz

[µTorrent 3.1.2 stable (26821)]

Another thing i notice is that i can override the automatic cache size and get rid of the disk overload when i crank it up to max (1800 MiB)' date=' but when a torrent is finished i get a "Flushing to disk (3388)" in the "Status" for that specific torrent.[/quote']

Maybe a specific-torrent related issue? Any link to it ?

And on a side note uTorrent is eating up 15% of my i7 quad core, where libtorrent-based clients such as qBittorrent / Deluge only uses 2% max even when hashing and down/uploading.

Maybe it is AV related ? Any screenshots ?

At that moment I was picking out random torrents from tpb just to max out my connection and to recreate the disk overload bug, so i can't remember that specific torrent. Later i got the same "Flushing to disk" but with a (32) instead of (3388). Don't think it is a specific-torrent related issue.

I have excluded uTorrent from Microsoft Security Essentials now, will see if that helps. Have no screenshots at the moment.

Nop still using 15% of my i7 quad core with AV disabled.

screenshot: http://bayimg.com/nAMoAAadG

[µTorrent 3.1.2 stable (26821)]

Another thing i notice is that i can override the automatic cache size and get rid of the disk overload when i crank it up to max (1800 MiB)' date=' but when a torrent is finished i get a "Flushing to disk (3388)" in the "Status" for that specific torrent.[/quote']

Maybe a specific-torrent related issue? Any link to it ?

And on a side note uTorrent is eating up 15% of my i7 quad core, where libtorrent-based clients such as qBittorrent / Deluge only uses 2% max even when hashing and down/uploading.

Maybe it is AV related ? Any screenshots ?

At that moment I was picking out random torrents from tpb just to max out my connection and to recreate the disk overload bug, so i can't remember that specific torrent. Later i got the same "Flushing to disk" but with a (32) instead of (3388). Don't think it is a specific-torrent related issue.

I have excluded uTorrent from Microsoft Security Essentials now, will see if that helps. Have no screenshots at the moment.

[µTorrent 3.1.2 stable (26821)]

Another thing i notice is that i can override the automatic cache size and get rid of the disk overload when i crank it up to max (1800 MiB), but when a torrent is finished i get a "Flushing to disk (3388)" in the "Status" for that specific torrent.

And on a side note uTorrent is eating up 15% of my i7 quad core, where libtorrent-based clients such as qBittorrent / Deluge only uses 2% max even when hashing and down/uploading.

Btw I'm on win7 x64 with uT 26710. And as i mentioned earlier my hdd is not the bottleneck, i can do 100mbis up and down concurrent with qBittorrent and Deluge.

[µTorrent 3.1.2 stable (26821)]

at what speeds?

100Mbit/s up and down

Nice

Actual speed (Concurrent up & down) ? Or max connection speed ?

False positive :mad: Getting disk overload again when seeding 10 and downloading 10 torrents...

I can max my speed and have concurrent 100mbis up and 100mbits down in eg. qBittorrent and Deluge, so my hdd is not the bottleneck. Sorry for the false hope :/

[µTorrent 3.1.2 stable (26821)]

No "Disk overload 100%" for me now with 26710.

at what speeds?

100Mbit/s up and down

[µTorrent 3.1.2 stable (26821)]

No "Disk overload 100%" for me now with 26710.

EDIT

DAME! Not any more... :mad: Getting disk overload again when seeding 10 and downloading 10 torrents...