First off, i take no credit for this tutorial, it is a copy from SCC posted by dashboardy. If requested i will remove this, i just thought it would be useful for everyone here as it has helped me a lot.

~~~~~~~~~~~~~~~~~~~~~

I've been asked a few times about the best settings for utorrent on a server, so I thought the easiest way to do this was with a guide. So, you've got a server with Linux (cause it's free or there was no option for windows) and you wanna use utorrent. NO PROBLEM. In fact if you take a look at the peerlists, the top seeders are usually using utorrent (and most of them are using linux/wine).

First, wine is a program that allows you to run windows .exe's in Linux environment. First thing you gotta do is install it. If you already have it installed, type the following in terminal/SSH

wine --version

If your version is between 0.9.40 and 1.1.5 you have a problem already. If you have wine version 1.0.1 (which seems like it's between those numbers) you're fine but other than that you gotta get rid of wine and install 1.0.1 or a version greater than 1.1.5. I recommend 1.0.1 as it is the latest stable build of wine, and has the fix for utorrent dropping peers (which is the problem with the other ones). Changelog for Wine 1.0.1 shows that it has fixed bug: 14188 utorrent - it disconnects fast leaching peers with Error 10022. Having had experience using wine 1.0 with utorrent, it is a very noticeable problem on a fast site like SCC.

Once you have ensured you have a decent version of wine, the rest is relatively easy.

wget http://download.utorrent.com/1.8.2/utorrent.exe

Download the latest version of utorrent, and while connected to your server via VNC or NX (or some GUI), bring up a terminal and type

wine utorrent.exe

You can install it or not, doesn't really matter. Now for the optimization.

First thing that pops up is the speed guide. You can click the dropdown box and scroll to 100mbit, but will still need to tweak a bit. Set the port between 60000 and 65000:



Now bring up Preferences, and match the following (I won't bother to type it out):








Other notable changes: Preferences, Advanced --> gui.delete_to_trash set to False. Note that I didn't include WebUI pages as these are easy to setup and you might not want one.

I've found these settings give much better performance than rtorrent and thus makes utorrent a very desirable client.

Other notes: I set max download rate to be 9500 KB/s to give the server a bit of headway. When you're leeching as fast as possible sometimes it slows down seeding/uploading, especially if it's a big torrent like a 1080p movie. 9500 KB/s is still very fast and gives the server that extra bit of breathing room.

ALSO: if you have a gbit connection you can increase the cache (if you have the RAM) and I would recommend limiting the download speed to somewhere around 20 MB/s, for the same reason described above. If you have SSD or RAID 0 setup on your server you may find you don't need to do this.

Additionally, I set the queue to download 3 at a time as leeching more than that at a time could have disastrous effects on your server's ability to torrent while those three are leeching. I personally set it to 2 myself.

Some additions - thanks to potholder for these:

some additional tweaks, and the reasoning behind them:

Options > Preferences > Advanced



bt.allow_same_ip - true - some multi-user seedboxes have many users and share the same IP address. if there are four users on one seedbox, on the torrent you have active, you will only connect to one of them. we want to allow all of them to connect.

net.max_halfopen - 100 - raises the limit of peers we can connect to at one time.

bt.connect_speed - 75 - number of connections to make each second, up to netmax halfopen limit

bt.no_connect_to_services - false - change the list or totally disable this option. some people may run their client on port 25, you never know...

bt.graceful_shutdown - true - makes the client wait to shut down (finishing tasks like announcing to trackers), rather than the regular quit which closes after 13 seconds regardless of what else needs to be done.

bt.use_rangeblock - false - after blocking a certain number of peers for hashfails, by default it blocks a whole range. not a good thing since seedboxes are often in the same range of ip addresses. I noticed this setting a few days ago when a large portion of server.lu boxes were blocked in my client.

you can find more info on advanced options here:
Advanced | BitTorrent