I haven't really kept myself abreast of any developments that may have happened in this regard, if anyone has any pertinent information I would be very happy to hear it. 
Azureus + NOD32 = still no workee?
- Thread starter Guden Oden
- Start date
Use bitcomet instead. Much MUCH lighter on resources and it has what you need from a BT client.
http://www.bitcomet.com
http://www.bitcomet.com
I don't recommend Bitcomet.
http://azureus.aelitis.com/wiki/index.php/BitCommet
http://azureus.aelitis.com/wiki/index.php/Super Seeding
http://azureus.aelitis.com/wiki/index.php/BitCommet
http://azureus.aelitis.com/wiki/index.php/Super Seeding
I've never had a problem with bitcomet maxing my connections with enough seeds.DarN said:
I do use azureus now, despite it's memory problem (leak? when I stop torrents it clears alot of memory), but bitcomet isn't some shoddy client.
You can use for weeks with good memory usage (30-60MB tops.. depending on disk buffer)
I didn't notice any significant speedups using the same trackers and peers etc.
I have had problems with azureus using upnp, it stopped working for some reason and I had to change the port, had to do that a few times now.
I also still easily hit 500-600 kb/s upstream also.
with a 512 rated upsteam.
DarN said:
well, i simply have to use BitComet cause i have 1.5 Mbit down / 192 kb up.
so there is no way i could DL really large file and have 1:1. i like that i can cap my upload for _ALL_ torrents i am DLing with BitComet.
if i had better conn i would gladly give more upload BW, but i simply cant.
people tend to forget that not everyone has same up and down speeds on their conns. just look at my ratio.... getting to 1:1 would mean either capping Dl also (which would take away all advantages of BT) or keeping client open forever, which is not an option.
I don't quite follow how bt works. I have a connection capable of 4 Mbps down and 512 kbps up. What would be the best settings in this case?
Right now I'm using azureus but never get connections greater then around 100 kbps and usually much lower, like around 24 kbps average. Is this normal, is bt just really slow?
Right now I'm using azureus but never get connections greater then around 100 kbps and usually much lower, like around 24 kbps average. Is this normal, is bt just really slow?
DarN said:Like I said, it takes a while. It's just considered good practice, you don't have to do it.silence said:
i know.
i just dont think that everyone who doesnt make it to 1:1 is leecher. i leave files for seeding when i can. but if you have multiple DLs, getting to 1:1 on something like 7 GB or more is close to impossible (with my connection).
i have cap at 15 KB up. if i put higher cap i cant even surf web...
thats all. i really wish i had like 4 Mbit up and down.
DarN said:
What good does capping your upload do for downloading? I wouldn't think it would make much of a difference, it will limit your peers download rates but it shouldn't effect your own should it? If everyone was uploading at much greater rates then we would all be getting faster download speeds, or am I completely off here. I do limit my upload to 40 KB/s but simply so my bandwidth isn't clogged.
Yup, actually I was getting NAT problems until I opened a port, now all is ok but it doesn't seem to have affected the download rates much if at all.
Bouncing Zabaglione Bros.
Legend
ANova said:
Because TCP/IP uses ACK(nowlegement) packets. If all your upstream is saturated, you can't sent ACKs quickly enough, so the end that is downloading to you slows down or retransmits whilst waiting for your ACKs.
Reserving a bit of upload for your ACKs means that you can send ACKs fast enough for the people sending to you not to be waiting around wondering if you got their packets - they send to you as fast as they can.
