Constant "disk overloaded"

[videofreak]

The disk overloaded notice is always displayed for me. I am using the latest utorrent 1.3.1 beta build 377.

I have used diskio.write_queue_size at -1, at 2^15 (32768) and tried 2^19 (524288). I have enabled diskio.coalesce_writes.

In the past utorrent would work with 3.5m byte/s up and down. Approximately 35m bit/s up/down. Utorrent runs from the windows system drive and downloads go to a dedicated 300gig Seagate IDE.

[Redleer]

there is beta 389 already try it out

[DreadWingKnight]

I am using the latest utorrent 1.3.1 beta build 377.

The current beta build is 389, not 377.

What is net.lowcpu set to on your system?

[videofreak]

Thanks for the info, I just upgraded to 1.3.1 BETA build 389. I had run check for updates but i guess as a beta it didn't catch it.

net.low_cpu is set to false.

The problem is still here but not as bad. Disk overloading seems to appear when both downloading and uploading approach 2.5MB/s. Then the disk overloaded flag will come on and downloading will stall to <50 KB/s while uploading contines at 2~2.5MB/s.

I set the global maximum upload rate to 1500 kB/s which seems to temperarly releave the problem. Unfortunately Downloading seams to mirror uploading at 1.2~1.5MB/s and never going above or back to its max of 3.5MB/s.

[1c3d0g]

Videofreak: you may also want to turn off diskio.flush_cache and see if that helps, but be aware that this will make µTorrent use more memory. :/

B.t.w, I'm jealous of your network speeds...

[videofreak]

I've set diskio.flush_files to false but it doesn't seem to make a difference.

I've upped diskio.write_queue_size to 524288 or 512MB and the disk overloaded problem disappears with a 1500K cap on uploading. Can utorrent acess more than 32MB of cache. Windows reports uTorrent mem usage at 22MB, VM size at 39MB and peak mem usage at 617MB.

Removing the cap and uploading returns to 2.5+ MB/s but downloading drops to <50KB/s. I nolonger sure the problem is all uTorrent prohaps my connection is just saturated.

I'm going to slowly raise the cap from 1500K to 2000K and report back.

Thank you everyone for your input.

[lorcro2000]

When you are downloading with 2.5MB/sec, there is a significant (albeit much smaller) amount of data going upstream as well to ack that the packages have reached you. If they don't get sent, the senders will choke the transmissions to you.

You need to have a cap on the upstream traffic or a proper router/firewall that can traffic shape and prioritize the packages going up to acknowledge receipt... m0n0wall can do this, for instance.

The easiest approach is to cap your upload, but that won't help if you have other things on your line uploading stuff the way a traffic shaping solution would.