Kazuaki Shimazaki Posted February 2, 2006 Report Share Posted February 2, 2006 Tonight, I began a download on a torrent with about a 95:5 BC/Azureus connection. After an HOUR of them ignoring me, all of a sudden, they (about 100 connected out of 1000 detected peers) suddenly decided to be ridiculously generous, and my download pipe was swamped to its flank speed - which turned out to be about 620KB/s for me, which sounds about right for a 6Mbps down connection. Since this does not happen often (a 600KB/s class is a first for me, in fat), I think I'd mention some things that I do not see most of the time at average speeds, in hopes it'd be useful to somebody.I'm using uTorrent BETA 1.4.1 build 413.1) Drag: I just noticed that uTorrent IS "human". When it runs at this speed, the program actually DOES bloat, fluctuating to taking up over 20MB real RAM. It also produces a significant drag on the system - it is about as much drag as Azureus when it is idling, which is significant but survivable. It is more drag than BC when idling. It was enough drag that I gave up my web-surfing and decide to take advantage of this valuable opportunity.This means I'd have to consider setting a cap at say 200KB if I start doing something important (like a game), just so this drag doesn't get to me...2) Disk Queue: The Auto Disk Queue management kind of falls flat at DL speeds of over 200-300KB/s. The problem is how to set it manually. I decided to use this rare occasion to do some experiments.diskio.write_queue_size defaults to -1, which is automatic cache management. µTorrent will automatically adjust the cache size based on your download speed (max measure download speed * 7). If you would like to adjust this value manually, set it 2 to 4 times your maximum download speed in kilobytes, but try to avoid going below 1000, or above 32768 in most situations.This advice plain doesn't work. To avoid an immediate disk overload alert, I had to set it to about 20 megabytes. Even then, a Overload came within a few minutes. I tried expanding it to 25MB and it still had occasional Overloads. Eventually I decided to leave it at 32768.3) Upload: At flank speed, I notice my upload was crimped to somewhere between 10-50% of its normal value. But that's OK, I'd be seeding for a long while for that torrent, because that torrent has a availability of only 0.770, and a thousand peers are waiting with me for the day when somebody would be nice enough to do a seed...If anybody got more of this kind of observations, maybe you can contribute too. Thank you. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.