• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

bittorent clients ... battle of the best

rh71

rh71

No Lifer
I have a 2800+ CPU (O/Cd too) + 512MB PC3200

Azureus vs. ABC ...

Azureus is a resource hog because of Java. 70MB footprint in taskmanager. I can hardly use winamp and firefox at the same time without it being noticeably lagging when starting something up. The JVM just kills.

ABC is much smaller but feels it needs to re-check all the torrents after unpausing (even the ones I'm just seeding) and large files mean long waits before anything kicks off. :| And it's quirky with the resuming... a file I just tried to resume (not finished downloading) gets checked to 100% then just goes right back to pause.

When it comes to nice BT clients... pick your poison. :| :| :| :|
 
Azureus runs just fine on my P3 800mhz laptop w/ 256megs of ram, I continue using it normally and don't even notice that stuff is downloading in the background.
 
Azureus works well for me. I don't notice it running while playing games at all, or anything else for that matter.
 
I know a lot of people don't understand this, so I'll try to offer a little insite. The JVM does aggressive garbage collection when its needed, and lazy garbage collection when it isn't.

You have 512MB of ram, oh my, its using 70MB. I'll bet you still have over 100MB free. If your system was actually approaching the limits of available system memory, the java garbage collector would be more aggressive in cleaning up. Aggressive cleaning takes processing time, so why waste the processor at a time when it isn't really needed? I know some people like to install gobs of memory and brag about how much they have free, but what's the point of spending money on memory that is never used?

If you've ever witnessed a program like Azureus or other major java application running inside a profiler you can witness this behavior. On a machine with less ram (or less available memory because other apps are currently using it) the program uses less memory. If it has memory to use, it uses it.

I'd rather not get into a major discussion about the different paradigms of progamming memory usage, but I'll say that the general theme followed by the garbage collection system is that unused ram is wasted ram.

It isn't the memory footprint that causes performance issues, unless that memory usage is forcing repeated use of the swap file. Somehow I don't see how Windows + Azureus + Firefox + Winamp could be using all 512MB of your memory. Are you sure you set everything up correctly?
 
I honestly don't know what makes Azueres or ABC that great, maybe someone could explain why? Up until now with all the "bittorrent client treads", I've been using the original program and it's been working fine..what's wrong with it?
 
Originally posted by: rh71
ABC is much smaller but feels it needs to re-check all the torrents after unpausing (even the ones I'm just seeding) and large files mean long waits before anything kicks off.
Click to expand...
when i start to re-seed, i press the re-seed button and it seeds pretty much instantly. am i missing something?
 
Originally posted by: rh71
I have a 2800+ CPU (O/Cd too) + 512MB PC3200

Azureus vs. ABC ...

Azureus is a resource hog because of Java. 70MB footprint in taskmanager. I can hardly use winamp and firefox at the same time without it being noticeably lagging when starting something up. The JVM just kills.

ABC is much smaller but feels it needs to re-check all the torrents after unpausing (even the ones I'm just seeding) and large files mean long waits before anything kicks off. :| And it's quirky with the resuming... a file I just tried to resume (not finished downloading) gets checked to 100% then just goes right back to pause.

When it comes to nice BT clients... pick your poison. :| :| :| :|
Click to expand...

if you put a file on hold in ABC it wont have to verify the data when you restart it. And it has never had to verify a file when i click the resume reseed it starts seeding it instantly.
 
Originally posted by: rh71
Azureus is a resource hog because of Java. 70MB footprint in taskmanager. The JVM just kills.
Click to expand...
BS. It's how the app's written and, as Kilsrat points out, how badly the memory is needed. You could easily write just such a hog in another language or a much leaner one in java.

I'm not sure where you'd do it but if you fooled around with it for a bit you could figure out how to specify a memory limit to the jvm. Granted, if it actively wanted all that extra memory (program design, not platform) it might not work all that well.
 
Originally posted by: joe360
I honestly don't know what makes Azueres or ABC that great, maybe someone could explain why? Up until now with all the "bittorrent client treads", I've been using the original program and it's been working fine..what's wrong with it?
Click to expand...
Well the advantage is that it's easier to manage your down/uploads because it's all there on 1 interface for you. I just tried BitTornado also and it's multiple windows (currently grabbing/seeding 6 files so it can be a clutter, even when minimized). It's too old-school. There's obviously going to be trade-offs, but I just want something manageable and doesn't spin my HDD for minutes before I can actually do the next thing...
 
Originally posted by: Kilrsat
I'd rather not get into a major discussion about the different paradigms of progamming memory usage, but I'll say that the general theme followed by the garbage collection system is that unused ram is wasted ram.

It isn't the memory footprint that causes performance issues, unless that memory usage is forcing repeated use of the swap file. Somehow I don't see how Windows + Azureus + Firefox + Winamp could be using all 512MB of your memory. Are you sure you set everything up correctly?
Click to expand...
I just ran some tests from a fresh boot (over 100MB RAM free after each scenario):

- Firefox (1 window) open, Azureus running 5 files... took Winamp 15 seconds to startup.
- Firefox (1 window) open, Azureus not open... took Winamp 2 seconds to startup.
Then: I decided to do it again... (closed Winamp)
- Firefox (1 window) open, Azureus running 5 files... took Winamp 2 seconds to startup.

Thinking it's not Azureus at this point (just that it takes apps longer the 1st time), but wait:
- Firefox open, Azureus running, Trillian just spun my HDD for 25 seconds before it decided to initiate.
- Firefox open, Azureus running, Trillian 2nd time opening, 5 seconds.
- Firefox open, Azureus NOT running, Mappoint (large map app) took 2 seconds to open up the first time.

How can it not be the hog ?
 
Maybe it's just the i/o. With 5 files you've got a decent amount of i/o going to different parts of your drive which could impede the loading of other programs. If you've got more than one disk, try having Azureus write to a different one than your programs are installed on.
 
Originally posted by: FishTaco
Did you try bitcomet ?
Click to expand...
This client looks great so far. Loads quickly the first time (can't say the same for Azureus), intuitive (same type of interface), lightweight (half of what javaw.exe takes), no "checking..." needed (trust!)... just what I ordered.

1 quirk with it... after pausing all files, it still uploads *something* consistently at about 20kbps according to DUMeter. I have to keep it shutdown instead when I'm not using it.
 
I just tried BitTornado also and it's multiple windows (currently grabbing/seeding 6 files so it can be a clutter, even when minimized). It's too old-school.
Click to expand...

I'm not sure if the Windows version has this, but on unix there's a curses version of each btdownload script and one of those is btlaunchmanycurses that runs many torrents in the same text Window although I don't personally use it because I use multiple instances of btdownloadcurses in screen.
 
Originally posted by: rh71
Originally posted by: Kilrsat
I'd rather not get into a major discussion about the different paradigms of progamming memory usage, but I'll say that the general theme followed by the garbage collection system is that unused ram is wasted ram.

It isn't the memory footprint that causes performance issues, unless that memory usage is forcing repeated use of the swap file. Somehow I don't see how Windows + Azureus + Firefox + Winamp could be using all 512MB of your memory. Are you sure you set everything up correctly?
Click to expand...
I just ran some tests from a fresh boot (over 100MB RAM free after each scenario):

- Firefox (1 window) open, Azureus running 5 files... took Winamp 15 seconds to startup.
- Firefox (1 window) open, Azureus not open... took Winamp 2 seconds to startup.
Then: I decided to do it again... (closed Winamp)
- Firefox (1 window) open, Azureus running 5 files... took Winamp 2 seconds to startup.

Thinking it's not Azureus at this point (just that it takes apps longer the 1st time), but wait:
- Firefox open, Azureus running, Trillian just spun my HDD for 25 seconds before it decided to initiate.
- Firefox open, Azureus running, Trillian 2nd time opening, 5 seconds.
- Firefox open, Azureus NOT running, Mappoint (large map app) took 2 seconds to open up the first time.

How can it not be the hog ?
Click to expand...
Because program startup is basically a disk i/o test, as Kamper noted. Your first test confirms that it is a disk i/o thing. The first time you load winamp the files aren't in the windows filecache, so it has to wait to move them there. When you close winamp and open it again it opens quicker because instead of reading the files from disk it is reading them from the filecache. Mappoint isn't doing massive disk i/o. Try opening winamp while extracting a large zip/rar file, or verifing a par set. Tada, slow load. Why? The disk is busy.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top