Optimizing Vuze (formerly Azureus) for Speed



optimize-vuze-for-speed-Vuze-frog-icon-imageThis guide shows how to speed up downloads in the freeware bittorrent client,  Vuze.  All bittorrent programs need to have their incoming and outgoing communications flow freely in order to achieve the highest download speeds and that is essentially what this guide is about.

There are a series of guides for using torrents here at Gizmo's Freeware.  Vuze is one of the suggested bittorrent clients at Best Free Bittorrent Client.

See also How To Use Torrents for links to the other guides, and other helful software reviews, here at Gizmo's Freeware.

I assume that you already have the installer from the download link in the Vuze Software Review.  

If you do not have Vuze, you can get it from the

This guide was put together using information given by the developers of bittorrent programs at their forums, guides and FAQs.  There are no secret tricks, just the real basics of proper set up of a bittorrent program.  Following these simple steps should result in increased download speed.

These are the basic principles of optimizing a bittorrent client, like Vuze, for speed: 

  • Choose a proper port to avoid ISP blocks and conflicts with other programs
  • Forward that port through any software firewall and router to allow incoming connections
  • Adjust internal settings based upon upload capacity of the internet connection to allow room for outgoing communications and to distribute upload efficiently. 

There are some programs that claim to optimize speed in Vuze.  Such programs are a scam and generally contain adware or spyware.  I have seen it said, by the developers of all bittorrent programs, that nothing will increase your download speed in a bittorrent client more than the basic steps set forth herein.

If you are not using Vuze,  there are several other specific guides for other clients and a general guide here:
Optimizing Bittorrent Clients

Before starting the guide, in Vuze go to Tools>Options>Mode (Azureus>Preferences>Mode in Mac) and set to Advanced.


Choosing A Proper Port

To avoid messing up a network connection that is already cleared, first check and see if your communications are blocked or are already clear. 

Testing The Port

Vuze has a built in port test located at Help>NAT/Firewall test.  Before using this test disable and blocklist as the Vuze server is on some blocklists.

The test will show the TCP and UDP (they should be the same, but do not have to be) port already chosen for Vuze. You do not have to change to the port show in the images here.  You should test both the TCP and UDP, by pressing the Test button.  This image has the TCP result - you want to see OK.


This is the result that you want to see for UDP


 OK (Success)-just go to Adjusting Internal Settings.   Error- follow all steps.

If you failed the port test above, then you should first set your port to a proper one.  The most important choice here is to avoid using a port within the 6881-6999 range. This was the range originally used by bittorrent programs and is often blocked by Internet Service Providers (ISPs). (If your port was in this range, change and re-test).

The safest choice is a port in the 49160-65534 range as this will avoid ISP blocks and possible conflicts with other applications.  This range used to be 49152-65534, but apparently Vista and Windows 7 grabs some of those ports in between.   Vuze-Wiki: Port is Blacklisted

Windows users, if you want to make certain there is no conflict.  Go to the command prompt and type in netstat -a >c:\log.txt  This will check to see which ports are being used and save a log text file at C:\.  Looking at the text file, you will know which ports to avoid.

In Vuze go to Tools>Options>Connection.  Depending on your Mode setting, you may only see one number



Forwarding The Port

A router will block incoming communications unless an exception is made.  All software firewalls will block incoming communications and most will also block outgoing communications, unless an exception is made.  If you are "firewalled", then other people will not be able to initiate connections with you (see Why Is Being Firewalled Bad).
As there are many firewalls and routers, this guide can not give explanations as to each.  However, there are guides available, on the internet for most firewalls and routers and this guide will link you to them.

Software Firewall - The permission should be set to allow TCP and UDP in both directions.  Generally, you will have a choice to set permission for  the Vuze port or for the Vuze program.  Setting permission for the port is the very slightly safer choice.

If you are forwarding the port only, then you should also forward port 49001 UDP (the mainline DHT port) in addition to the main port above. You can check these options for guides:

Router - There are two choices here.  The easier way is to use UPnP.  However, this has a possible security issue.  Using UPnP allows any program to create a port mapping through the router without consent of the owner.  Note:  Given the recent findings of Rapid7 regarding security flaws in UPnP, it is generally suggested here that manual forwarding be used.  If you still want to use UPnP, then it would be a good idea to test and see if your device is vulnerable to attack through UPnP.

The other choice is to manually forward the port through the router.  This does not have that security issue, but involves going through several steps to accomplish.  Using the guides linked herein, this should not be that difficult and is the preferred method.

You should set a rule for the port number chosen above and then you should set a separate rule for Port 49001 UDP as this is the port that the mainline DHT uses. 

UPnP (NAT-PMP in Apple) - The Easy Way Enable UPnP (NAT-PMP for Apple) in Vuze and router.
Automatically refresh mappings when NAT status is "firewalled"  should also be enabled.



Manual Forwarding

  1. UPnP (NAT-PMP) must be disabled in Vuze (see Images above). 
  2. Use the Static IP Guide.
  3. Set permission for Vuze port you have chosen, This should be set to allow both TCP and UDP communications.. Port 49001 should also be forwarded, but  for UDP only.
    You can check these options for guides: 

Click Here to Re-Test Port    Success-Proceed to next step.   Error- re-do steps or seek help in Forums.

Adjusting Internal Settings

The  most important setting here is to cap upload in Vuze to 80% of your overall upload capacity.   Setting upload in Vuze is a fine line.  The more upload you give, the more download you will get from other peers. However, if upload is set too high, or to unlimited, then download speeds will suffer as outgoing communications (acknowledgment signals, resend requests etc) will be interfered with. Other adjustments are made here to distribute your upload so that you receive back the most download from other peers.
This section of the guide is based on the Vuze-Wiki: Good Settings page.

You should be in Mode = Advanced.as stated at the begining of this guide.

Speed Test: Speedtest.net (Click for Test)
First the upload capacity of your internet connection must be determined by taking an online speed test.  Speedtest.net has test locations worldwide and will highlight the one closest to you.
To take the test you must have Flash installed and javascript enabled.

Before taking the speed test, press Settings in the upper right of the speedtest.net page.  This will take you to another page.  At the bottom of that page is the "Global Settings" options.  Set "Speed Measurement" to kilobytes and press "Save" .  This will facilitate entry into the calculator below and will lessen confusion as qBittorrent shows speeds in kilobytes.





You should stop all internet activity, including torrents, before taking the test and the test should be taken a few times to obtain a reliable average. Results will now show in KiloBytes. It is the upload rate that is important here.


Another Way To Test Upload Speed
For most people these test results will be reliable (Comcast users see Note).  However, you may wish to do a double check on real life upload speed.  When you are seeding a torrent with a good number of peers and you are using your upload cap, set upload to unlimited and watch for about 5-10 minutes and see where upload settles in at.  Then input that number into the calculator in the kiloBytes section. 

Note:  Some ISPs will show inaccurate results on the speed test.  If your ISP has anything like Comcast's PowerBoost, then your results will show higher than the actual speed of your connection.  PowerBoost provides a burst of download and upload speeds above your provisioned download and upload speeds for the first 10MB and 5MB respectively.  Since the speed test involves relatively small files, this will skew results upward. 
If you have PowerBoost, or something similar, my findings from my own results and those of others is that the actual speeds are 60% of the test result.  So if you get 200kB/s for upload at the test, you should enter 120 in the kB/s box in the calculator.  Using Google ("speed result" x .6) will get the proper number to enter in  the calculator and this actually turns out to be very accurate.  You should end up with the calculator showing a cap that is about half of the test result.

Calculator Azureus Upload Settings Calculator
Once you have an average upload speed for your connection go to the online Azureus Upload Settings Calculator. Although designed for Azureus, this calculator will work for all bittorrent clients.
This calculator was created by the8472 a contributor to Vuze (fka Azureus) and part of the team that created Bittorrent Protocol Encryption.

Enter your average upload speed in the appropriate box


The calculator will automatically give the proper figures to adjust various options in µTorrent.


Input Results Into Vuze - Screen shots of locations in Vuze of settings to be adjusted

Tools>Options>Transfer            Azurues>Preferences>Transfer


Do not enable the "Auto" setting


Tools>Optoins>Queue                Azureus>Preferences>Queue


Peer Sources & Encryption

Having the proper peer sources enabled, such as Peer Exchange (PEX) and Distributed Hash Table (DHT), will help download speeds as they will help you find additional seeds and peers for a torrent. 
Encryption was primarily designed to thwart Internet Service Providers interference with bittorrent.  Having encryption enabled and allowing incoming legacy (non-encrypted) connections will provide you with the largest pool of seeds/peers to select from.

The settings for peer sources are at Tools>Options>Connection and should be set as in the below image:


The settings for encryption are at Tools>Options>Connection>Transport Encryption.  The settings shown in the image below will provide the highest encryption level and still allow connection with the most seeds/peers:


Mainline DHT Plugin

I now suggest the use of the Mailine DHT plugin in setting your Vuze up to get the best possible speed.  The DHT enabled in the step above is the Vuze implementation of DHT and is used by a minority of users.  The vast majority of users utilize the DHT implemented by µTorrent.  Installing this plugin will allow you to connect to both the Vuze DHT network and the µTorrent (or Mainline) DHT network.  This most likely will not make a difference on very healthy torrents, but on smaller torrent swarms may be a great help.

Since this guide is getting long enough, I decided to put the instructions for installation of this plugin on a separate page.  Please go to Vuze Help:  Installing The Mainline DHT Plugin for instructions.  It is a very simple installation process.

Good Torrents

The general rule here is to choose torrents that have a high seed to peer ratio. Seeds have 100% of the content associated with the torrent and are only uploading to peers. Peers also upload to other peers, but are also looking for other peers to upload to themselves and their download capacity is almost always higher than their upload capacity.

This applies even though one swarm has significantly more active users than another. For example, a torrent with 30 seeders and 70 peers (30% seeders) will generally be faster than one with 500 seeders and 2500 peers (20% seeders) as the average upload capacity available to the peers will be higher. (TorrentFreak).

For more information see Good Torrents

Related Articles

Gizmo's Best Ever Freeware Forums

If you still have issues after using this guide and would like some assistance, you may post here or our Forums.  The comments section here is not well set up for ongoing discussions, so the forums are a better place.

When posting on a speed issue, please provide

  • Your speed test result for both upload and download speed in kiloBytes per second (kBps)
  • Your result at canyouseeme, both before taking any steps and after.  Just indicate Success or Error do not post your IP address.

If you have a suggestion or correction for the guide, please post here.

Those who wish to post a thanks may post here or in the forums. I always appreciate hearing from those who this helped and I do read the posts regularly. I used to respond to each thanks, but realized it was clogging up the comments section. I thank all those who have posted their appreciation and all those who will.

So, to those who post a "Thanks", I appreciate it.



Please rate this article: 

Your rating: None
Average: 4.5 (314 votes)


Sorry I was on the road when this was posted and unable to respond. If you are still having issues (and get this reply), what is the model number of your Netgear? Have you set exception in your software firewall? It is also possible that the DSL hardware has a firewall built in. What is the make and model of this hardware? Steve

No worries Steve - appreciate the follow up!

Got a Netgear DGN-2200 and (AFAIK) set the exception properly for the firewall.

This piece is both Router and DSL modem, so I don't think that there's a second firewall hiding anywhere - yes?

Looking at this guide at PortForward, it looks like you need to go to the Port Forwarding / Port Triggering link and select Port Forwarding. http://portforward.com/english/routers/port_forwarding/Netgear/DGN2200/A... The guide forwards port 6881, but you should use one of the ports within the range mentioned in this guide. Also, be sure to set a static IP first. Did you set exception in your software firewall (if any)? Steve

I thought I managed to figure it out - although my router/modem didn't have the same options as shown at portforward.com. (Supposed to click on "Port Forwarding / Port Triggering" - which wasn't even there!)
Went through "Services>Inbound Services>Add" and was able to enter the Static IP there. Applied the changes and now Vuze is downloading at 275 kB instead of around 60kB - which is a vast improvement.
However, an hour or so later I'm back down to 80 kB again -
When I run the NAT/Firewall test from Vuze I get a 'fail' and am told 'Connect attempt to 172.12.22.xx:xxxxx (your computer) timed out after 20 seconds. This means your port is probably closed" - The IP address shown isn't even in the same realm as the static one I setup.

I probably need to call NetGear and find out how THEY recommend someone do port forwarding since "Port Forwarding / Port Triggering" doesn't appear on my CP at all...

Thanks for your help Steve - much appreciated though!


ps - logs show "[DoS attack: TCP SYN Flood] multi-source syn flood attack in last 20 sec , Monday, Jul 01,2013 10:27:16" repeatedly does this make any sense?

Was this provided by your internet provider? If so, it may have a different interface. Who is your ISP? Does your screen match the one on page 21 of the user manual here? http://support.netgear.com/product/DGN2200v1 Not sure where that log is from, but it most likely is just a result of the test attempting to get through (if the times match). Steve
They have changed over at PortForward recently and I am not a big fan of the new look and it appears that their screens are outdated (or just wrong) in your case. Anyhow, we can work through the manual now. From what I see, you first have to create a service and then set an inbound and outbound rule allowing the service. To set a "Service" for Vuze, see page 48. You can name the service "vuze" and allow TCP and UDP. The start and finish port should be the same port number you have chosen for Vuze. Then go to page 44 to set up an outbound and then an inbound rule for "vuze". Basically the same info will go into both rules, enable = yes, service = vuze, action = allow always, LAN and WAN options = any, logging = never. Also, I forgot to mention that the IP Vuze will return is your public IP that is shown on the internet. The Static IP is just between the router and your computer. Hopefully, this will get you going. (fingers crossed). If not, then you can try UPnP (page 85) enabling on the router and in Vuze (see above). Steve

Thanks again for your help Steve - I think we've got it working as well as it can now with my (less-than-steller) ISP. Hitting speeds up to 200kBs, which is probably the best I can hope for these days.


Well I hope it sticks this time. Steve

mmm something weird happened to me now... yesterday I followed this guide and it worked wonders, but today, the smiley face is yellow again, speed cap back at ~ 100 kb/s, and when I do the NAT/Firewall test it throws errors... I tried changing the port (both in Vuze and forwarding it in the router configuration) and do the test again, but still the same... btw this is what the NAT/Firewall test says:

"Testing port TCP XXXXX ...
NAT Error - Connect attempt to yyy.yy.yyy.yyy:XXXXX (your computer) timed out after 20 seconds. This means your port is probably closed.

Testing port UDP XXXXX ...
Sending outbound packet and waiting for reply probe (timeout=5000)
Sending outbound packet and waiting for reply probe (timeout=10000)
Sending outbound packet and waiting for reply probe (timeout=15000)
Sending completion event
NAT Error. Inbound test failed, timed out."

Any help? Went throw the full guide again and idk what's wrong :(

I am sorry for not getting back to this sooner. I have been on the road without internet access most of the time. If you are still having the issue, the first thing that comes to mind when a router is involved and the connection was open and then closed, is that a Static IP was not set. If a static IP is not set, then the rule will become useless if the IP changes. Did you set a static IP? Steve

Honestly I don't remember what I did, but I solved the issue somehow and I have a working Vuze now; thanks anyways :)

That is good to hear (no matter how it got done). Enjoy Steve

This guide is great. My speed in a given torrent rised from like ~ 100 kb maximum to ~ 350 kb average. Thanks a lot!!