StarDestroyer.Net BBS

Until about two months ago, I had settled on BitSpirit. It wasn't bad but for all its claims about memory efficiency and all that, it slowed my computer to an unusable crawl. Handling only one file merely improves that to barely tolerable.

So I switched to Azureus. It seemed better than BitSpirit. But it still seemed to drag quite a bit. Besides, for some reason, BitComet doesn't want to give data to Azureus (at least for me). I would have thought it an illusion, but I remember something on that once about BitComet being a leecher that doesn't want to give...

So, faced with a new torrent which is distributed completely by people running BitComet, I downloaded BitComet on the theory that BitComet won't screw its fellow users. So far, the theory is working, and alas, my computer is still working at a decent speed. But that's just one torrent and one impression, so I want to ask:

1) Does BitComet really not give data to users of other clients?
2) Which, in your experience, is the least demanding client in terms of not slowing down your computer to a dastardly crawl...

Thank you.

I use BitTornado, which at times likes to fully utilize my CPU, but I get around that by placing it at "Below Normal" priority so that all other programs get priority access to the CPU.

Like Uranium, I use Bittornado myself. I find it to be a nice and functional minimalist client, without the messy java interface of azureus.

Bittornado is the client that most fits your specifications, but with some caveats that you may or may not care about. It mangles non-ANSI filenames beyond recognition (a problem on Japanese torrents), has difficulties when running more than one torrent simultaneously (you have to micromanage bandwidth allocation for each, something that Azureus would handle automatically), and will sometimes refuse to shut down completely, instead hanging as a process in the background hogging 100% CPU (but doesn't use much RAM). The last can be dealt with by forcing its priority down and making sure it's shut down after you're done, but the other two are better dealt with via using Azureus (which is currently the only Bittorrent client I know of that can handle non-ANSI characters well).

I haven't noticed BitComet acting like you've mentioned, but I have a small list of trackers that I normally use. I know that there's a hacked version of BitComet which will spoof share ratio, but more stringent registration-only trackers will catch this and boot it.

I've used both BitComet and BitLord (essentially bitcomet with a slightly modified interface), and had the same problems as you. It either wouldn't upload when leeching or seeding. I also has problems uploading ratios to trackers, which could be a problem if you tried to use it on sites stringent about ratios.

I've stuck with Azureus, but ABC was fairly good when I used it. It didn't seem as processor or memory intensive as Azureus, so might be worth a look.