Archived

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

Firon

µTorrent 1.9 alpha 15380

Recommended Posts

The issue I listed above is still occurring in 13559:

[2008-12-01 22:22:12] ㈸¬w Download from RSS|stuff.avi has started downloading.

Share this post


Link to post
Share on other sites
The issue I listed above is still occurring in 13559:
[2008-12-01 22:22:12] ㈸¬w Download from RSS|stuff.avi has started downloading.

Can you provide the feed where this occurs?

Share this post


Link to post
Share on other sites
Ok, same logs with the 13560 build, instead of the previously posted 135(50?) build. Speed issues persist.

http://www.mediafire.com/?sharekey=f5c39b45f46327e9d2db6fb9a8902bda

(Same link, file name of uploaded file reflects build)

What about CPU usage of the logging build? Was that reasonable / improved? I guess the question is whether the logging build 13560 transfered at a slower rate than the non-logging build 13559.

Share this post


Link to post
Share on other sites

I actually tried the non-logging one first(59) before I realised (60) was also available, I saw no significant difference between the two, cpu wise. I did notice the non-logging one sorta spiked the speeds when it first started up, then cut them back down to silly-slow speeds, that did not happen with the logging one. It just started up and was slow. Could be random network awesomeness, or something else, I'm not sure.

Share this post


Link to post
Share on other sites

What kind of internet connection do you have? What is the ping time to google.com when uTorrent is not running? What about when it is running with uTP+TCP, and also when it is running with TCP only?

Share this post


Link to post
Share on other sites

What kind of internet connection do you have? What is the ping time to google.com when uTorrent is not running? What about when it is running with uTP+TCP, and also when it is running with TCP only?

1.25mbits/s down, 312kbits/s up,

32ms without utorrent

Reply from 209.85.171.100: bytes=32 time=33ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

52ms with uTP only

Reply from 209.85.171.100: bytes=32 time=36ms TTL=242

Reply from 209.85.171.100: bytes=32 time=60ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

Reply from 209.85.171.100: bytes=32 time=81ms TTL=242

134ms with BOTH

Reply from 209.85.171.100: bytes=32 time=163ms TTL=242

Reply from 209.85.171.100: bytes=32 time=118ms TTL=242

Reply from 209.85.171.100: bytes=32 time=122ms TTL=242

Reply from 209.85.171.100: bytes=32 time=136ms TTL=242

52ms with TCP only

Reply from 209.85.171.100: bytes=32 time=47ms TTL=242

Reply from 209.85.171.100: bytes=32 time=35ms TTL=242

Reply from 209.85.171.100: bytes=32 time=93ms TTL=242

Reply from 209.85.171.100: bytes=32 time=34ms TTL=242

These times taken(Where it applies) roughly 1 minute after the client had started, I have 4 torrents that are running.

Share this post


Link to post
Share on other sites

Can you sample again? That really doesn't seem right... Maybe something else was happening on the network at the time? Are you setting rate limits? Try turning the rate limits off, sample that way too.

Share this post


Link to post
Share on other sites

Sure, re test with 1 minute startup time, I'll time it this time. Also, all caps have been removed(IE Unlimited).

(I am, other than my Mother, the only one on the network, and she only browses internet/email, doesn't download)

Without utorrent 32ms

Reply from 209.85.171.100: bytes=32 time=33ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

Reply from 209.85.171.100: bytes=32 time=32ms TTL=242

Reply from 209.85.171.100: bytes=32 time=33ms TTL=242

With utorrent uTP only 81ms

Reply from 209.85.171.100: bytes=32 time=134ms TTL=242

Reply from 209.85.171.100: bytes=32 time=33ms TTL=242

Reply from 209.85.171.100: bytes=32 time=76ms TTL=242

Reply from 209.85.171.100: bytes=32 time=84ms TTL=242

With TCP only 133ms

Reply from 209.85.171.100: bytes=32 time=33ms TTL=242

Reply from 209.85.171.100: bytes=32 time=34ms TTL=242

Reply from 209.85.171.100: bytes=32 time=291ms TTL=242

Reply from 209.85.171.100: bytes=32 time=177ms TTL=242

With BOTH 69ms

Reply from 209.85.171.100: bytes=32 time=95ms TTL=242

Reply from 209.85.171.100: bytes=32 time=109ms TTL=242

Reply from 209.85.171.100: bytes=32 time=36ms TTL=242

Reply from 209.85.171.100: bytes=32 time=39ms TTL=242

Note: the first time I tried to do it on both, it crashed(for this run.)

EDIT: the Crash was not a full crash, it froze up and thus left no dump or logs :/

Share this post


Link to post
Share on other sites

I did a test for seeding several torrents (no downloading) on 1.9beta 13559:

With both uTP and TCP enabled, I get around 45kByte/sec upload and nothing ever goes above 50

With only TCP enabled, I get 55kByte/sec and occasionally up to 70kByte/sec

With only uTP, I got 45kByte/sec but since not every client supports uTP it isnt a fair test.

I take it the uTP protocol is not quite optimized, as using just TCP?

Share this post


Link to post
Share on other sites

Hi.

I'm testing the last alpha build and I meet 2 issues:

1/ When I start the client my multitracker torrents jobs are vely long to update the announces!

And after few minutes 4 or 6 announces become active but the others stay stuck in updating state.

When I quit the alpha and restart the latest 1.8.1, trackers become active very quickly.

If you want to test it, I can post my (public) multitracker list (~20).

2/ I have the feeling that the "uTP state" written on the right of each IP in the Peers tab vanishes with the time: when the peer list is growing, many recent uT clients displays [uTP] but after 5 or 10 min this code disappears...

Is it a normal behavior ?

Share this post


Link to post
Share on other sites

First-time poster; long-time lurker...

Something that I'm unclear of: If I enable uTP in v1.8.1, is this the exact same thing as using v1.9? In testing this with both clients (on an unthrottled ISP), I get very similar results in UL/DL speeds, with no hiccups running build 13559 in WinXP SP2.

Additionally, how is it that I can identify specific v1.9 users in the peerlist, since all [uTP] peers seem to come from v1.8.1 and BT6.1.x? -Thanks!

Share this post


Link to post
Share on other sites
1/ When I start the client my multitracker torrents jobs are vely long to update the announces!

And after few minutes 4 or 6 announces become active but the others stay stuck in updating state.

When I quit the alpha and restart the latest 1.8.1, trackers become active very quickly.

If you want to test it, I can post my (public) multitracker list (~20).

Is it a normal behavior ?

What build are you experiencing this on? 13485 certainly had this problem, 13559 should not...

Share this post


Link to post
Share on other sites

No it's the latest alpha given in the first post of Firon:

utorrent-1.9-alpha-13559.upx.exe

EDIT/ I retested again and the update of tracker announce in 1.9 runs longer than in 1.8.1 even if announce finishes to display "working".

Screens of my test, 20s after the start of uT.

uT 1.8.1

http://img523.imageshack.us/my.php?image=stable181po6.jpg

uT 1.9

http://img227.imageshack.us/my.php?image=alpha19pu5.jpg

Share this post


Link to post
Share on other sites
What about CPU usage of the logging build? Was that reasonable / improved?

No. I still can't use any of the logging builds, locks up uTorrent completely within seconds.

Share this post


Link to post
Share on other sites

Same for me. uTorrent 1.9 freezes my Windows within seconds. High CPU usage.

Interesting I managed to finish one downloads. Everything was fine. Then I put 2 downloads and when I came back to utorrent to see if they are done,it was frozen. I killed it with task manager. Restarted. uTorrent started checking the torrents and stopped responding again.

Share this post


Link to post
Share on other sites
Same for me. uTorrent 1.9 freezes my Windows within seconds. High CPU usage.

Interesting I managed to finish one downloads. Everything was fine. Then I put 2 downloads and when I came back to utorrent to see if they are done,it was frozen. I killed it with task manager. Restarted. uTorrent started checking the torrents and stopped responding again.

The logging build, or the regular build?

While it's frozen, you could capture a crash dump and send it to me:

In Vista, use Task Manager. Right-click the process and select the option to create a crash dump.

In XP:

ntsd.exe -p 4100 -e 4100 -c ".dump /mf c:\jit.dmp;q"

where 4100 is the PID, and c:\jit.dmp is the resulting dump.

Share this post


Link to post
Share on other sites

Very slow speeds; I get throttled at a minimum of 20kB/s, however I'm now getting speeds of ~1.5kB/s using the new client (1.8 beta and 1.9 beta)

http://codepaste.appspot.com/show?id=5330

http://codepaste.appspot.com/show?id=5331

**Edit**

Okay, so now its working fine I think but its not by-passing the throttle; Maybe thats not what it was suppose to do but still it was a very very very very good + :D

**Edit 2**

Wow it still drops to 0.2KB/s and etc

Share this post


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