Increase download speed

From VuzeWiki
Jump to: navigation, search

You want to download faster?

Make sure that

Just click all those links and read the info carefully... After reading that you may ask questions about that topic in the forums.

Test the speed before complaining[edit]

If you get green smileys HealthOk.gif as torrents' "Health", then you know that your basic network settings are ok. However, that doesn't guarantee speedy transfers.

It is good to understand that

  • there is no central server from which you download. Everything that users download, is at the same time uploaded by users
  • you contact other users for your downloads
  • respectively, others should be able to contact you (NAT & port forwarding to be configured)

It is quite possible with a "new" torrent or an one with "small" swarm (only a few peers), that the missing pieces are not available. So, it is quite possible that torrent remains active with "downloading" status, but is not actively downloading anything as there is nobody to download from.

Before thinking that your configuration is slow, test it with a "known speedy" torrent. E.g. the following torrent has very high speed:

It is a Ubuntu Linux distribution, which has lots of seeders, and you should reach your internet connection's maximum speed in most cases (especially with ADSL/cable home connections). Speeds well over 10 Mbit/s (= 1 MB/s as Vuze sees it) should be reachable. You don't have to download the 700 MB torrent completely, but you can use it as a test case for measuring maximum speeds of genuine torrents.

Another user complete download = faster download for you[edit]

Another reason for uploading is simply to help fill everyone up. By doing this you prevent someone, who is seeding, trying to upload a part you already have (and which is useless for you). The chance that he then uploads a piece you need becomes greater. This will not result directly in increasing speed but it will optimize the uploader's upload which results in you getting your piece sooner since you no longer need to wait for a piece. Think of it as a reverse Zero Sum game.

More Things To Know[edit]

It is very important to know that, when you are seeding, or uploading a torrent, the u/l speed of your sharing is not the only thing using your upstream bandwidth. Requests made to the tracker, browser requests to load web pages, and sending email all utilise your upstream capacity. So you may experience the following difficulties when running Azureus.

  • "Unable to locate server..." error message whilst browsing the web
  • Connection problems
  • Other web related issues

If you find yourself having problems with the Internet while Azureus is running, try further lowering your max upload.

The point of this section is to explain that when configuring your maximum u/l setting in Azureus, it is best not to set it to use all of your upstream capacity. Rather, it is best to set it to use a maximum of 80% of your total upstream bandwidth.

A note on ADSL speeds using PPPoE:[edit]

An ADSL connection using PPPoE has reduced usable bandwidth compared to the theoretical bandwidth that is purchased. In my experience a theoretical 512kb/s dl product has overheads due to the PPPoE encapsulation that limits the connection to about 400kb/s max. This means the limit before applying the suggestions above should be 400/512 ≈ 78% of the theoretical bandwidth. This logic applies in both directions. So Azureus DL max would be:

80% × 78% × 512kb/s ≈ 319kb/s; 319kb/s ÷ 8 B/b ≈ 40 kB/s if Azureus is the only Internet application. Reduce this somewhat to allow other Internet protocols better response on the same connection.

A tip for RcvWin/TcpWindowSize tweakers[edit]

When you are using a Windows OS you can also use the TCP Optimizer to optimize several system settings for your line speed.

"I've most often seen [poor performance] with people running on Windows who 'tweak' their TCP send and receive buffers to be very large in search of higher bandwidth. Buffered data is obsolete data and causes serious problems in the responsiveness of the protocol to changes in the peer state. Since data and requests share the same TCP socket, buffering lots of data means that your request for a block may have to wait 10's of seconds before it even gets transmitted, by which time the peer you are talking to may have decided that you aren't interested in his data after all, or your own client may decide that the peer you are talking to is snubbing you. Either of these is disastrous to download rates."

Final Note:[edit]

Trackers get uncountable numbers of requests made on them every day. I have seen that some people think that clicking on the "Manual Update" button will somehow increase their speeds or make an offline tracker come back online quicker. It Will Not. Clicking on the Manual Update button is for last resort checking when there is a connection problem On Your End. For example, if you are using a proxy for your tracker requests, you may need to perform some manual announces to verify that the proxy is working while you play with the settings. Also, some private trackers require peers to be logged in on their web page before they can connect to the tracker, adding the IP they logged in from to a whitelist. In this case it may be necessary to announce manually after you log in.

In any case, the more you click on the Manual Update button, the more this will destabilize the tracker, and cause it to go offline for everybody. So for the most part, Leave the Manual Update button alone, and your speeds will recover by themselves (unless there are other issues, but anyway, this button will not help to fix those either).

Read the Azureus FAQ