Support NeoGAF

[borghe]

just really started looking into this client. it's queueing and autostopping for seeding just rules. I have like 20 torrents queued up and ready to go. talk about taking bittorrent to the next level. and with first piece option turned on (and non-avi files) it acts very similar to how kazaa and napster did back in the day...

sweet..

 

[Dead]

Yeah, but its such a resource hog -_-

 

[StoOgE]

also, make sure you get it off of their website. There are versions with spyware.

 

[FoneBone]

Is there any way to select individual files from a multi-file torrent, though? Doesn't seem like it...

 

[Sriram]

To select indiviudal files, double click a torrent (while its downloading) and go to the files tab. Then a list of files will come up. From there right click and select high priority, normal or do not download.

 

[Diablos]

Yeah, but its such a resource hog -_-

When I was running 512MB it certainly was... 1GB/dual channel seems to allow apps like Azureus run without hogging any resources. SATA helps, too.

The one thing I don't like about Azureus is that it forces you to always upload.

 

[Zaptruder]

When I was running 512MB it certainly was... 1GB/dual channel seems to allow apps like Azureus run without hogging any resources. SATA helps, too.

The one thing I don't like about Azureus is that it forces you to always upload.

modern computing *needs* 1 gig of RAM nowadays... any less and you'll be chugchugchugging.

 

[borghe]

The one thing I don't like about Azureus is that it forces you to always upload.

What do you mean?

As far as I can tell Azeurus only "forces" you to upload up to a 50% share rating.. and frankly if you stop sharing before 50% (well, before 80% IMHO) you are a torrent leach who deserves to be shot on sight.

the first priority only let's you go down to 50% share rating. however after that 50% you can change settings in the seeding ignore section that stops after various criteria (share rating, seeding time, number of peers or seeds, etc). so for example I tell it to ignore all torrents that I've seeded 120% share rating on (150% at work). I have it set on my cable line for 2 downloads and three total torrents. So right now when I have like 20 files queued, it will only download 2, start downloading a third as soon as one of them is done, then likely start seeding the second one (so only download one and seed two) until the first file hits 120% share, then drop off the first seed and start downloading a second (the fourth total file), etc.

and if someone wants to quit before 50% share rating and be a piece of shit leech on society, they can always just cancel the torrent right after it finishes downloading.

 

[Mejilan]

I've been using Azureus for about a year now and it truly is fantastic.

However, it only became TRULY amazing when I finally figured out how to forward my ports, thus turning all of those nasty yellow smileys to BRILLIANT green ones.

 

[Zaptruder]

http://www.portforward.com/

 

[Deleted member 1235]

The one thing I don't like about Azureus is that it forces you to always upload.

Isn't the states largely not bandwidth capped?

 

[Manabanana]

The only thing Azureus rocks is your resources Just my two cents.

 

[borghe]

I guess I'm just not seeing this momery usage that some of you are complaining about.. are you using the most recent anureus? the most recent jre? i have been running it non-stop now with those 20 torrents (of which about half are finished) and it's peak memory usage is like 77MBMB This is on a Athlon2400 with 1GB. BitTornado on the same box runs up to 75MB per torrent that I have seen... Actually to think about it, with the torrents I am running, BitTornado would probably be right around where I am at (25MB per torrent). So I am failing to see where this is a resource hog compared to other clients...

 

[Great King Bowser]

Azureus is great, but I keep getting these annoying pop ups when I start it.

Also, when I have azureus running in the background, my internet will start chugging along. Firefox will take ages to load pages, and sometimes straight up refuse to load them. What's going on?

I used to be able to torrent in the background whilst surfing the interweb, but on my laptop nowadays I have to choose to use the internet, or torrent using Azureus.

 

[borghe]

Azureus is great, but I keep getting these annoyong pop ups when I start Azureus.

if you mean the donation popups, just tell it you never want to donate.

if you are saying actual ad popups, you got spyware.

 

[Great King Bowser]

No, it was a popup from Azureus.

Something like:
Mapping incoming peer data port (TCP/4355) has been reserved by [IP]...

Probably because my router designated me a different IP the other day, so all my port forwarding had to be changed. Strangely it's stopped now.

But my internet still chugs.

 

[Teknopathetic]

BitComet >>>>>>>>> Azureus. Same features, Not a resource hog. I actually leave BitComet open for a large part of the day and seed because it doesn't facefuck my computer.

 

[Gattsu25]

wait...you can set azereus to stop a torrent after you seed a certain amount?

also...stopping a torrent before you have uploaded at least 100% is bullshit IMO...my minimal seed % is 120% though I often have it go beyond 200% with the way my up/down ratio is

 

[borghe]

wait...you can set azereus to stop a torrent after you seed a certain amount?

also...stopping a torrent before you have uploaded at least 100% is bullshit IMO...my minimal seed % is 120% though I often have it go beyond 200% with the way my up/down ratio is

yes. long story short, under Tools->Options->Queue->Seeding->Ignore just setup a share ratio to whatever youwant it to be. you can also then stipulate to keep seeding regardless of share ratio if there are less than x seeds. So I have mine set to 120% (1.2:1) but to seed no matter what if there are fewer than 1 seed in the swarm.

 

[jenov4]

The only thing Azureus rocks is your resources Just my two cents.

Amen. It's such a fucking resource hog. It's because it was written in shitty java.

Also remember you have to install that Java resource kit thing which is an additional 20 megs or so.

 

[Great King Bowser]

Seriously, why does my internet start crawling as soon as I start torrenting? It pisses me off.

Happened with ABC, but not as bad as it does with Azureus where Firefox becomes unusable.

 

[borghe]

Well, I have installed and am running bitcomet, and frankly, I think all of you guys are smoking crack saying azureus is anything but typical. CPU utilization is completely the same between Azureus and BitComet (a little higher with BitTornado but that is probably because another entire app is started for each torrent with bittornado). Memory usage between all three is pretty much the same also.

and my test bed is checking where Azureus was right before I stopped it and starting up the exact same torrents (leeches and seeds) in bitcomet.. memory and cpu usage is identical. and my computer performs the same as well...

so either your computers are behaving differently or it is in your heads. I will give you it could be your computers or something, but on my system all three clients pretty much run at the same level.

If you are having resource issues with Azureus, is is probably some underlying problem with your computer.

 

[borghe]

Seriously, why does my internet start crawling as soon as I start torrenting? It pisses me off.

Happened with ABC, but not as bad as it does with Azureus where Firefox becomes unusable.

if you are saturating your upload, it will cause the internet to crawl.

all connections on the internet generally require your computer to send a request or acknowledgement packet to the remote computer. if you are saturating your upstream, it makes it impossible, or very difficult, for your computer to send those packets. so even though you are only using say 512Kbps of your 4Mbps downstream, because you are using all 384Kbps of your upstream for upload your computer essentially has a hard time requesting or acknowledging receipt data.

in general it is recommended to limit your total global upload on any bittorrent client to 80-90% of your total upstream. more like 70-80% of your total upstream if you plan on using the internet for stuff other than bittorrent. (remember, on clients like shad0w, bittornado, and the original bittorrent you will have to limit each instances upload rate so that the total upload between all instances falls in between that 70-90% range).

 

[milanbaros]

Just a general queston. Why does it say 98.8% complete when it has done 9.90GB of 9.91GB? Surely that would be around 99.9%?

 

[Jeffahn]

Just a general queston. Why does it say 98.8% complete when it has done 9.90GB of 9.91GB? Surely that would be around 99.9%?

Azureus will discard chunks which have failed the hash-check, thus avoiding the corruption problems experienced with a network like Fasttrack. You'll probably always end up downloading slightly more in all than the actual file size you end up with.

...

 

[borghe]

actually all clients do that (it is part of the bittorrent protocol spec). The problem is that azureus counts that as downloaded. so if you downloaded 10MB of bad data, that 10MB extra is still counted in your ratio. I mean the amount of bad data you get is generally miniscule, just kind of a sticking point that you then end up compensating for bad data with good data :\

 

[Liu Kang Baking A Pie]

if you are saturating your upload, it will cause the internet to crawl.

all connections on the internet generally require your computer to send a request or acknowledgement packet to the remote computer. if you are saturating your upstream, it makes it impossible, or very difficult, for your computer to send those packets. so even though you are only using say 512Kbps of your 4Mbps downstream, because you are using all 384Kbps of your upstream for upload your computer essentially has a hard time requesting or acknowledging receipt data.

in general it is recommended to limit your total global upload on any bittorrent client to 80-90% of your total upstream. more like 70-80% of your total upstream if you plan on using the internet for stuff other than bittorrent. (remember, on clients like shad0w, bittornado, and the original bittorrent you will have to limit each instances upload rate so that the total upload between all instances falls in between that 70-90% range).

If anyone's BitTorrent is killing their Internet, it's not because of uploads. Do you seriously believe he's consistently uploading 256kb to 512kb of info at all times?

Usually, it has to do with how many active connections you have and your router or modem not being able to handle the size of the table. You can turn off all NAT options in the program, but outside of that, you're having typical problems. It's usually caused by a shitty router, but you never know.

 

[borghe]

umm.. you are wrong. the majority of problems come from saturated uploads. 384Kbps is only 48KBps. Taking into account TCP overhead realworld throughput is lower than that. usually around 44KBps (the fastest speed I have been able to sustain on my 384Kbps connection for a single upload)

and if you have more than one torrent going, aka you are attached to more than a single swarm, yes, you will almost ALWAYS saturate your upstream unless you rate cap it.

the typical modern day pc/nic/router can handle hundreds of TCP connections without even batting an eye. the problem usually lies in saturating your upstream.

http://wiki.theory.org/BitTorrentFAQ

Q: BitTorrent lags the hell out of my computer. I've got cable and a 2.6ghz processor. When I get like 3-4 or more Torrents going, my computer and connection are very laggy. What's wrong?

A: Cable usually has a very large download capacity , around 2Mbit /sec, but a very limited upload capacity , usually 128 to 256Kbit/sec , and often poorly queued. Running a bunch of BitTorrents will rapidly chew up that thin upload capacity causing your network connections to lag (even downloads require your computer to send out some packets). A solution is to limit your upload rate to about 75% your upload capacity to allow for overhead. Alternatively, there are clients (such as ABC) that consolidate multiple torrent downloads into a single program, and have a global upload limit.

4) max_upload_rate is not set and the upload is saturating your modem

You can tune BitTorrent by increasing your upload limit slowly from about 75% of your maximum and finding the point where your download speed begins decreasing instead of increasing (best done on a torrent with many seeders). That peak is the best setting for your upload limit.

 

[Teknopathetic]

Borghe: Nah, Azureus is just a hog. If leave Azureus on overnight, the next morning it takes a handful of seconds just to wait for the screensaver to finish shutting down. Firefox (not loading pages, just it's performance in general), bogs down especially when multi-tasking between it and other programs. The resource utilization between the two aren't even comparable.

 

[borghe]

eh, I don't see it, however my previous post was not talking about resources, just network connectivity. if you run one or definitely more torrents without capping your upload, you will pretty much trash your internet connectivity, well, assuming your upstream is capped at some ridiculously low number (384Kbps, even 768Kbps will usually become saturated). it doesn't matter which client you use...

as for azureus' resource issues (or java in general) I guess it depends on your computer. I don't have a single problem with azureus or java.. some java apps are insanely slow (Series 60 Theme Editor......ugggghhhh), but most are just fine. I guess it depends on the computer.

 

[Teknopathetic]

borghe: Yeah, that much I know (the internet connectivity), I usually cap mine at around 30kBps on a 384kbps upstream.

 

[Great King Bowser]

Thanks for the explanation guys, I'm trying out BitComet now though, getting 100kb/sec download at the moment! I usually don't get more than 50kb/sec tops. But it's stayed consistent for the past hour.

I'm on cable here in the UK, 1mb down, and only 128kb up. So I should set my limit to around 12kb/sec?

I've got it on 9kb/sec just to be on the safe side, and my internet is running fine.

 

[borghe]

remember that there is ALWAYS going to be TCP overhead... so if you set your cap to 12KBps on a 128Kbps, you probably won't be able to use the internet very well though your bittorrent should run just fine. if you want to use the internet as well, yeah, 9KBps is probably a good number to start with. That should allow you to still get ok downloads with bittorrent and still be able to use the internet decently. beware though... 9KBps isn't that great in the grand scheme of bittorrent. you will probably want to put it back up to 12KBps when you are done using the internet.