Switeck

That was the special upload slot global choker method added by alus. uTorrent v2.2 betas had this as well, but it was removed and replaced with the older upload slot handler from v2.0.4 in v2.2 stable release because of this and other problems with it.

I have no clue how many connected peers/seeds you had, or their distribution between torrents. If uTorrent needs UPnP to get port forwarding working on your network...that comes as no surprise. If your router's support of UPnP is really bad/broken, UPnP can also be a disaster...

tyrael, Limit your upload to 600 KB/sec and see how well it runs...because that may be about all you really have. You can upload more by setting upload speed limit very close to max than you can running with "unlimited" upload speed. 2nd link in my signature...your line limit much more closely matches 5 mbit/sec upload than anything else, although even that's too high for the 3 mbit/sec time period. You could use Scheduler to lower upload and maybe download as well during the slower hours, but Scheduler won't reduce the number of connections used at once. So use fewer global connections -- even 200 may be as much or more than your router can bear. Reduce connections per torrent to only 40-60. Since you don't have 10+ mbit/sec download speed, you likely will not have a download speed loss from doing this...it might even increase download speeds slightly. Set upload slots per torrent to 10 (upload to 10 people per torrent at once). And test with the "use extra upload slots" UNCHECKED...I've seen it reduce my upload speed if checked because it started way too many and was giving low speeds to each person at once instead of much higher to fewer. It is better to upload faster to 10 people per torrent than slow to 25, because of torrent piece sizes. Even at a piece size of 512 KB, if you're uploading to someone at 1 KB/sec they'll need to wait ~8.5 minutes before they'll have a new piece to share to someone else. Only completed pieces can be shared, so long delay between completing pieces hurts. If/when you're only seeding, reduce connections per torrent to only 15-20. With fewer connections, you'll upload MORE per day as less is wasted as overheads. If you need UPnP, enable it in uTorrent. But if UPnP works for you, you shouldn't need NAT-PMP also in uTorrent...and having both enabled can cause problems on some networking equipment.

Seems pretty normal. It'll probably be quite hard to get overheads much lower. Maybe by reducing connections and turning off a few features...but reducing too far runs the risk that uTorrent may not download as fast all the time.

What's wrong with that overhead?You're downloading at 500-600 KB/sec and that causes ~16 KB/sec upload overhead in ACK packets. That's about 3-4% overhead on the upload side from downloading. It used to be as high as 35%.

I already changed the chart recently once because of forum changes...only to find out this message forum doesn't handle a lot of text formatting in predictable ways. And there are no tabs. The monospaced fonts did not work at all. Neither did the font point size.

uTorrent v2.2 RC5 seems to have a weird flashing box that appears at the top of its window. I tried to reproduce its location in my screenshot here: http://img210.imageshack.us/img210/1715/ut22flashingbox.png It covers part of Down Speed and Up Speed column headers in my window, and seems to very quickly flash white/black and disappear. Attempts to screenshot it failed, although I tried roughly 100 times to "catch" it visible -- so I drew it on the screenshot I made for demostration purposes. My guess is it's a separate window that much like the mouse cursor simply isn't captured in the screenshot using the Print Screen key. The location of this box seems a fixed distance from the top and left of uTorrent's window and does NOT depend on what column is lined up with it. It seems like a data entry window/box briefly appearing that shouldn't be there. I'm using bog-standard Win XP PRO SP3, 1 GB ram with very little else installed.

martix, can you give an example?

https trackers are indeed encrypted, as are sending the tracker updates through a proxy or VPN -- though they're "in the clear" past that point.

If you're not doing tracker updates in the clear, protocol encryption can still hide the nature of the traffic, but not the amount or the destiations.

Ty Witt, test with servers in Western Europe...like in Germany, France, and England. My guess is you only get very high speeds with ips in Romania...but uTorrent needs to know your rest-of-the-internet speeds or your international connection will probably always be overloaded.

Yes, leave it if you have nothing else downloading/uploading in uTorrent. Are you getting tracker errors on it?

If the speed graph doesn't show it's been uploading...sometimes...then technically it hasn't. But that doesn't mean you're not OFFERING to upload, if/when a peer comes along.

You should only need uTorrent to download torrents, not any add-on "helper" program/s to go with it. Most "uTorrent speedup pro!" type programs are complete bullshit snake-oil, some even contain spyware/malware!

So the highest upload speed settings I recommend are the 800 kbit/sec ones in 2nd link of my signature. Try the 1st link in my signature and rafi's uTorrent v2.0.X Migration Guide here: http://forum.utorrent.com/viewtopic.php?id=74820

Yes, only use 1st link in my signature if that didn't help.

kidzmo, speedtest.net -- what results do you get there?

Same as above. Your upload has not changed appreciably. uTorrent's settings are based on upload, not download.

Assuming there's no burst speeds that can't be sustained more than a minute, you should probably be able to use 1 mbit/sec upload settings or at least 900 kbit/sec upload settings.

I heard awhile back that TCP will be phased out in uTorrent in favor of uTP.

mcaspi, once you find hardware is broken...you can't change the software around to "fix" it. That's the scenario I'm talking about -- LOTS of routers are hopelessly broken, but not so many that we should just give up on uTorrent entirely. And if your ISP is mangling networking packets, uTorrent is limited in its ability to detect such corruption/slowing because many ways the ISP uses are going to resemble a lot of other causes/effects.

If you're on ADSL, you probably have at most 1 mbit/sec upload bandwidth...maybe even as low as 0.25 mbit/sec (256 kilobits/second) upload! There are links above my chart and a caption below it to explain the terms a little more.

If the problem is on their end, because they're using horribly broken networking software/hardware...there's not much that can be done through testing.

arjhen47, you seem to be on a very hostile ISP (Bell ADSL ISP in Canada) that attacks its customers' traffic -- destroying or corrupting it.

mcaspi said, "If that is so, why not disable uTP in those cases by software. I (2.0.4) download at 20-30 kB/s from a Bittorrent 7.0 peer using tcp. uTP drops it to 0." Because some peers/seeds now only work with uTP. And as you're seeing, others might only work properly with TCP. I've got my end set up to receive incoming uTP connections but not make any outgoing uTP -- letting the other ends decide what to use. To get uTP incoming only, but TCP both ways... Set bt.trans_disposition to 29.