Azureus has the best multi-torrent GUI, the most features, the best speeds and the best performance behind a NAT Firewall (BitComet is nothing but a leech client and it's so called NAT Traversal blows, I've done speed tests with Azureus, BitComet and Bit Tornado and Azureus blew the other two away).

The only bad thing about Azureus is Java. Azureus itself uses very little cpu and ram. It's the javaw.exe which Azureus needs to run which uses the most system resources. If you are having high cpu troubles then make sure you are using the latest Java Run Time Environment from http://java.sun.com It should be version 1.5 update 2. I run Azureus on an AMD K6-2 550 cpu with 512mb RAM running WinXP and the main resource problems I have with Azureus is javaw.exe 's RAM usage.

Azureus.exe and Javaw.exe should use hardly any CPU at all if your system is configured properly. javaw.exe is definately a RAM hog. This isn't Azureus's problem, it's Sun's problem because they make Java, so complain to them for the memory problems, here's their forums: http://forum.java.sun.com

BitComet is great if you are a leech or like getting banned from as many trackers as possible. Azureus once got banned from trackers too but the developer fixed it ages ago, probably because it's open-source and things get fixed alot quicker if there is a decent number of devs or someone who isn't even a dev. can send in a fix because anyone can download the source code.

In the BitComet forums at http://bitcomet.p2pforums.com the developer hasn't posted a fix or some kind update status as to when the tracker bugs will be fixed. His last post was: Thu Nov 11, 2004 8:22 pm, the last version of BitComet 0.57 was released on Mar 5, 2005 and there isn't even any new beta versions to try and fix the problems: http://download.bitcomet.com/deve/

He hasn't even fixed this bug: http://www.p2pforums.com/viewtopic.php?t=3845
CSX Wrote:
"BitComet is running on:
CPU :
RAM size : 127.49 MB
OS Version: Microsoft Windows 98 SE
This is shown, when I run BitComet on my old PC which has an AMD K6 266mhz MMX
only a small thing, but the Client is running just fine on it"

Then the developer "RnySmile" says this:
"woo! my K6 266 only have 32M memory(still in use ^_^), yours has such a large memory."

So not only does he have the hardware with the problem, but he can now reproduce the problem himself, see what's causing it and fix it.

No wonder the leech bug hasn't been fixed.