Archived

This topic is now archived and is closed to further replies.

Heres_Johnnnny

utorrent = 5kB/sec. Azureus = 60kB/sec on same torrent!

Recommended Posts

I was trying out utorrent and set it to dl a torrent (2mbit adsl). I noticed hours later it was crawling along at 5kB/s. so I closed utorrent and set the torrent to continue in azureus. It immideatly began running at approx 60k/sec. So I for won't be using utorrent and will revert to azureus. dunno why there was this clear difference but 1/10th speed is not good.

Share this post


Link to post
Share on other sites
So I for won't be using utorrent and will revert to azureus.

Thanks for letting us know.

Anyways,

It's been said before but, It's hard to compare speeds between clients, since it's not always the client - It's the peers you connect to.

Share this post


Link to post
Share on other sites
I was trying out utorrent and set it to dl a torrent (2mbit adsl). I noticed hours later it was crawling along at 5kB/s. so I closed utorrent and set the torrent to continue in azureus. It immideatly began running at approx 60k/sec. So I for won't be using utorrent and will revert to azureus. dunno why there was this clear difference but 1/10th speed is not good.

its always settings, im sure you have not just taken Az right out of the box and used it, I never did, had to tweak that out as well. Have fun. I do.

Share this post


Link to post
Share on other sites

i will admit azureus is extremely fast even out the box. on private trackers utorrent works great and gets good speeds but on any public trackers ive struggled to get above 40kB/s when i have maxxed out when tested it on azureus. not entirely sure why that is but its happened with nearly every public tracker torrent ive tested both utorrent and azureus with.

Share this post


Link to post
Share on other sites

I've maxed my connection, both up and down, on a single torrent from a public tracker before. It's all in the peers you connect to.

Share this post


Link to post
Share on other sites

I keep hearing azureus is fast out of the box with no tweaking so why is it that utorrent comes with a so called crap set of defaults? Surely we are shooting outselves in the foot if we don't get the defaults fixed or are we just making excuses. DHT may well be a factor in this guys speed issues but it will be interesting once DHT is implemented what the excuse will be if it continues. Please, if you are all convinced it is bad default values put in a feature request to get the values changed so that people get the same experience speed wise as azureus. I personally don't think it's the settings but I keep hearing it so...

Currently it seems like it's analogous to asking a car owner to go into their engine management unit and start tweaking the map sensors and the like so the car works smoothly. Sure some of can do it and know how but most don't.

Just for the record I don't have a problem with speed but then again I like to tweak so I never use defaults.

Share this post


Link to post
Share on other sites
It's been said before but, It's hard to compare speeds between clients, since it's not always the client - It's the peers you connect to.

I disagree. If you let a torrent run for a bit and you get 60k with client A and if you try another client and get 5k for client B and go back to client A and get ~60k then it's pretty straight forward which is faster. At the end of the day it doesn't matter what the reason is for client B going so slow you just won't use it. I've done such comparisons in the past which have led me to bitcoment/utorrent as preferred clients. I don't like Azureus because it just so excessively slow starting up and consuming memory than I believe is adequate.

Share this post


Link to post
Share on other sites
Please, if you are all convinced it is bad default values put in a feature request to get the values changed so that people get the same experience speed wise as azureus. I personally don't think it's the settings but I keep hearing it so...

Now why would we do that when we all have different PC's & Internet connections? IMO, U set values based on those 2 things.

It's been said before but' date=' It's hard to compare speeds between clients, since it's not always the client - It's the peers you connect to.[/quote']

I disagree. If you let a torrent run for a bit and you get 60k with client A and if you try another client and get 5k for client B and go back to client A and get ~60k then it's pretty straight forward which is faster.

Thats somewhat true if they both 'right out the box.'

Lets try this as an example: Az vs. uT on a Win98 PC w/ 64MB Ram that has Intergrated graphics using 24MB Ram. So the available Ram U have is 44MB. U see where Im going, right? Again, the settings based on ur PC & Internet connection.

Another main thing is that some clients have a SP2 limit work around built in. I know Az and Bitcomet do. if a client doesnt have a work around built in, u may need the patch. Whether it helps give u more connections or more connections faster is debatable. But I do know It helps me get connectable. So it can be the client that is making the speed difference. And, connectable=more connections=better speeds.

Some info from Bitcomet on event 4226:

http://www.bitcomet.com/news/20040908_xp2_4226.htm

Share this post


Link to post
Share on other sites

I haven't done much tweaking on µTorrent. I'm quite happy with the 40-100 kB/s I usually get (from public trackers), since I'm using my conection for other things as well ;)

But yesterday, just seconds after starting a download, I had it d/l at 200 kB/s.

So yes, it very much depends on the torrent.

µTorrent works just fine.

Share this post


Link to post
Share on other sites

Personally to complain about download speeds is just ridiculous. I mean, what is it that you want to download so fast that you need it "now now now, here here here, fast fast fast"? Doesn't anyone have patience anymore?

Comparisons of speeds between the two is just nearly impossible. It's been said time and time again that it'll depend heavily on the peers you connect to. Sometimes you get better peers on one time and others you get crappy peers. It's happened before and you should just deal with it.

There's little reason to compare this client to other clients in terms of upload or download speed/performance. That's something that'll always be trivial until there's a surefire method and technique to test this (more likely on an isolated test-only tracker). One can, however, compare uTorrent to other clients in terms of memory consumption and CPU usage.

It seems there are people who complain about the speeds whereas I don't care and just let the BitTorrent client do its thing. It's going to complete eventually if you're getting something that's well seeded and healthy. I mean, who complains about download speeds? Are you trying to get the latest warez and porn? :P

Share this post


Link to post
Share on other sites

uTorrent is one of best client !

Personally i have a poor internet connection 128/1024 and i have always good DL/UP speed.

My config:

MB D865PERL Intel Corp. - BIOS RL86510A.86A.0089.P21.EB, 23/02/2005

P4 HT 2.6 Ghz 1,5Go RAM - NVIDIA 5900ZT 128MB DDR (ForceWare 71.84)

2 HDD MAXTOR 80Go P-ATA 8Mo cache

2 HDD MAXTOR 80Go S-ATA 8Mo cache RAID0 (Stripe) 128K blocks

WINXP Version = "5.1.2600.2180 (xpsp2.040803-2158)"ADSL 1024/128

uTorrent:

Port: 2005

Max Con: 512

Max Con per torrent : 128

Max upload slot: 8

Upload limit: 8-12 depend on internet traffic

Net.low_cpu: false

Net.max_halfopen: 30

Share this post


Link to post
Share on other sites
Please' date=' if you are all convinced it is bad default values put in a feature request to get the values changed so that people get the same experience speed wise as azureus. I personally don't think it's the settings but I keep hearing it so...[/quote']

Now why would we do that when we all have different PC's & Internet connections? IMO, U set values based on those 2 things.

Yet I keep hearing that azureus is better out of the box regardless. Remember I don't know whether it's true or not but for those advocating that there is a nice compromise on default values azureus has chosen then maybe we should do the same in utorrent.

Thats somewhat true if they both 'right out the box.'

Lets try this as an example: Az vs. uT on a Win98 PC w/ 64MB Ram that has Intergrated graphics using 24MB Ram. So the available Ram U have is 44MB. U see where Im going, right? Again, the settings based on ur PC & Internet connection.

I have to admit I'm not clear on your point. At the end of the day if you load up both clients on the same PC with the same internet connection and one performs better than another then you can say that that client is faster for you and maybe we need a review site or two which is objective to tell us that if you have a low end machine spec then utorrent is better than azureus but otherwise it may not be. Again I don't use azureus so I don't know I'm just thinking out loud. At the end of the day I think you have to pick what a "common" spec PC for today is and use that as your baseline if you where to do a review. I would has it a guess that if you can afford an internet connection you have a PC that is more than capable of running most clients without problems. If you want to play games and stuff while torrenting that's another issue and imho not relevant to the speed argument for obvious reasons. Regardless there is nothing stopping you doing a test yourself to see which client is fastest for you.

Another main thing is that some clients have a SP2 limit work around built in. I know Az and Bitcomet do. if a client doesnt have a work around built in, u may need the patch. Whether it helps give u more connections or more connections faster is debatable. But I do know It helps me get connectable. So it can be the client that is making the speed difference. And, connectable=more connections=better speeds.

Some info from Bitcomet on event 4226:

http://www.bitcomet.com/news/20040908_xp2_4226.htm

And so you have a client which if if has not implemented SP2 limits is shit slow and not worth the time regardless. At the end of the day I'm not too worried whether a client reaches steady state speed in 5 minutes or 10 minutes just so long as the difference is not stupidly large. What is of interest is the range of steady state speeds that are reached.

As to your news about this limit rating it was fixed a while back with bitcomet fyi. I'll apologize ahead of time if I'm wrong but I think you don't understand the issue with event 4226 because you seem to imply that you are being limited by your peers client choice because of it. This limit is only applicable to outgoing connection you make and not incoming connections to your PC so you are not being limited by your peers client doesn't have this limit patch in it's client. The reason is that you are requesting a connection with them (so they exist and you exist) and there will be minimal time completing the connection so you are not waiting on anything. Event 4226 comes into play because you send out a connection request and wait. If the peer doesn't answer you wait for a default time. Enough time that other connection requests start piling up and you hit the limit. Not sure if that is clear but I hope you get the idea.

To give you a unbiased opinion I am hangin for utorrents dht feature but until that day bitcomet is the superior client for torrenting in it's purest form without being a resource hog like azureus.

Basically bitcomets speeds are comparable at least to utorrents and often are better especially when tracker troubles arise or you have a hard to find file you want to track down.. That is a fact for me which is why I've shelved utorrent until dht is here. To be honest the only reason I'm keeping an eye on utorrent is because I love the built in scheduler. Fanastic feature for a bt client.

Share this post


Link to post
Share on other sites
Net.low_cpu: false

what does it actually do? connecting faster or downloading faster but taking more cpu loading time? i have a fast cpu so it's not a problem.. actually i haven't seen any problems till now, downloading at maximum speed

Share this post


Link to post
Share on other sites

What I meant was that if a person has the 4226 event, and their client doesnt have a work around and they dont use the patch, it will effect them. I didnt mean me. What I shoulda said was that I used the patch to go from un-connectable to connectable. Not by connecting to someone who was using the patch.

I used that extremely low end type of PC as an example cuz we all dont have the same PC setup. Some torrent users are still running Win98. Some only have 64MB Ram w/Intergrated sound and graphics. Hell, Some are even still using dial-up. LOL!!

That BitComet link was the only BT client that I know of that had officially addressed 4226 on their site. I learned about 4226 way b4 BitComet found out about it. I learned about it when SP2 first came out. To my knowledge, Shareaza was one of the first to address it and update their client accordingly.

PC's, Internet connections, seed/peers, client settings all effect speeds to me. Its just the PC's, Internet connections and Bt clients can be tweaked. (some might not know abut MTU, TTL, TCP Recieve Window, etc in regards to their Internet connection.)

And u right about Az seeming to be better out the box. I even said that in another post. Az has different default settings in their advanced options than uT. Some ppl suggest changing some advanced settings in uT to increase speeds. So Im contradicting myself right now. :P Maybe we should ask for different default settings, especially in the advanced options. (which I think someone did asked for and is going to be in the later versions of uT, if Im not mistaken.)

Share this post


Link to post
Share on other sites

1.1.8 takes care of the connection attempt limit by limiting it to 8 connection attempts (the same amount as Azureus). uTorrent's default settings will be adjusted to work better. :P The cache will be increased slightly by default, flush files will be on by default, diskio.write_delay will no longer be changeable, and possibly other changes.

Share this post


Link to post
Share on other sites
1.1.8 takes care of the connection attempt limit by limiting it to 8 connection attempts (the same amount as Azureus). uTorrent's default settings will be adjusted to work better. :P The cache will be increased slightly by default, flush files will be on by default, diskio.write_delay will no longer be changeable, and possibly other changes.

and DHT is up and working.. I have been in IRC 24/7

=] =] =]

1.1.8 testers are so lucky rawr..

Share this post


Link to post
Share on other sites

so i keep hearing that argument time after time "its not the client its the peers you connect to!!" as if peers have nothing to do with the client. If client A consistently gets faster speeds then client B OBVIOUSLY client A is faster. The peers you connect to are directly related to the client.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.