µTorrent Community
You are not logged in.
This build is NOT suitable for general use.
New alpha! The main change is that uTP (UDP torrenting) is added and enabled by default. It also has real-time transfer rate control and latency minimization.
This build will probably download slower than 1.8.1, particularly if the entire swarm is 1.8.1.
--- 2008-12-02: Version 1.9 (build 13582)
- Change: add independent TCP and uTP, and queue length stats to Statistics dialog
- Fix: another fix to trackers stuck in "updating..."
- Fix: PEX address parsing bug
- Fix: New Download message from RSS feed
--- 2008-12-01: Version 1.9 (build 13559)
- Fix: TCP connection queue when using uTP (fixed trackers stuck in "updating...")
- Fix: re-connecting too quickly to peers when using uTP
- Fix: crash/corrupt text with Advanced button in Add Torrent dialog
--- 2008-11-24: Version 1.9 (build 13485)
- Feature: uTP with rate balancing
Download here: http://download.utorrent.com/beta/utorr … 82.upx.exe
If you have a crash, run the uncompressed build and upload the dump files to www.mediafire.com
What is not in 1.9:
UDP hole punching (yet?)
UDP tracker
What is in 1.9:
uTP, the micro transport protocol. This UDP-based reliable transport is designed to minimize latency, but still maximize bandwidth when the latency is not excessive. We use this for communication between peers instead of TCP, if both sides support it. In addition, we use information from this transport, if active, to control the transfer rate of TCP connections. This means uTorrent, when using uTP, should not kill your net connection - even if you do not set any rate limits.
What was in 1.8.1:
uTP, but connection attempts were not initiated by default, and there was no control over TCP as described above. You can enable it, but likely you will see the uTP connections not transfering much data, because they are pushed out of the way by TCP.
What this means for rate control:
You are still free to set rate limits and use external limiters. The "Automatic upload rate" control is flawed enough for most people that it will likely be removed once uTP is well tested and deployed, since it entirely supercedes that feature.
How to enable and disable it:
Preferences > Advanced, set bt.transp_disposition to:
255 - both TCP and uTP (default)
10 - uTP only
5 - TCP only
If you are experiencing slow upload or download performance please try 13583, which should generate "socket.log" and "utp.log". You don't need to run it for more than a minute or so once the transfer rates stabilize. Post both log files for us to look at. http://download.utorrent.com/beta/utorr … 83.upx.exe
Last edited by alus (2008-12-02 17:05:48)
Offline
Add a torrent > press "Advanced..." in the Add Torrent dialog to trigger a crash. Also, tracker updating seems a bit... slow. Crash dump: http://www.mediafire.com/?jj1imyz1ymt
P.S. uTP?
Offline
Is there a recommended router NAT udp "connection" timeout value?
Offline
I experience almost the same crash as GTHK, but my utorrent first crashes when i click on the advanced tab in the advanced window.
http://www.mediafire.com/download.php?mmzje4gzm0d
in add torrent -> advanced the field "trackers" contain hieroglyphs and maximum download rate, maximum uploade rate have weird values
http://www.mediafire.com/imageview.php? … mp;thumb=6
Offline
那就算了~
Trial for a while。
Offline
How about a change-log with the rest of the changes (not related to the "main change" ) ?
edit:
found this about uTP : http://forum.bittorrent.org/viewtopic.php?pid=391#p391
Last edited by rafi (2008-11-26 10:29:23)
Offline
New alpha!
Nice :-) I was wondering when the next alpha's/beta's would be comming.
The main change is that uTP (UDP torrenting) is added and enabled by default.
Confused. What is that supposed to be? UDP tracker capability, UDP hole punching or ...? Where is more info?
It also has real-time transfer rate control and latency minimization.
Same here, more info please. Both can mean a lot of things.
Sidenote; I didn't see any options in the Advanced Settings to control these functions.
Offline
using the latest alpha and noticed the tracker is stuck at updating.. already restart utorrent, recreate firewall rule and the problem still persist
Offline
Testing it now... I didnt get a crash but there is a major lag when you start up the program and all the torrents initialize and connect to the tracker.
Ive got about 15 torrents seeding and 1/2 started to seed instantly then after 2 minutes the rest of the torrents went green.
Firon could you could look at that...see if you get that.....
I didnt get the crashes everyone else has been getting im running on server 03 and no probs apart for the lag.
Offline
GTHK wrote:
Add a torrent > press "Advanced..." in the Add Torrent dialog to trigger a crash. Also, tracker updating seems a bit... slow. Crash dump: http://www.mediafire.com/?jj1imyz1ymt
Fixed, thanks!
Offline
rafi wrote:
How about a change-log with the rest of the changes (not related to the "main change" ) ?
edit:
found this about uTP : http://forum.bittorrent.org/viewtopic.php?pid=391#p391
Not true. UDP trackers are unrealted to uTP.
Offline
fowl wrote:
Is there a recommended router NAT udp "connection" timeout value?
30 seconds.
Offline
DHT "update" seems to never stop. sames goes for tracker updating
Offline
How long has uTP been in uTorrent? I'm seeing uTP connections to both uTorrent 1.8.1 and BitTorrent 6.1.1. Which means that the announcement is wrong.
Offline
uTP is new to 1.9.
Real-time rate control and latency minimization means µTorrent can auto-throttle speeds if other bandwidth-intensive applications need it, so that it doesn't end up saturating the bandwidth. It's possible because of the flow control possible only through laying the protocol on top of UDP.
Offline
It is not new to 1.9. 80% of connections to 1.8.1 are uTP. So it is in some form in 1.8.1 as well, which also explains the announcement about 1.8.1 peers.
Rate Control and Latency minimization are nice, but, how do they work out if your router or software on your computer is doing the same? E.g. I can't turn on automatic bandwidth control in uTorrent because it gives impaired performance.
Offline
@niksus: It basically lays BitTorrent on top of UDP, which provides for better flow control, no TCP RST packet attacks, and probably other stuff I'm not thinking of off the top of my head.
Edit (2008-12-01): For clarification, the fact that TCP RST attacks are nullified by this change is a side-effect of the move to UDP, and was not the motivating factor that led to its implementation. uTP was in the works long before it was discovered that Sandvine was using the aforementioned tactic to interfere with BitTorrent traffic.
@Klaus: uTP has been in the works for a long while now, and parts of it have made their way in to previous versions little by little. Whether that explains what you're seeing, I don't know, but uTP (at least in its current, now mostly-complete, and actually actively enabled form) is new to 1.9.
Last edited by Ultima (2008-12-01 16:30:07)
Offline
i have a problem all my seeding torrents are all stuck at queued torrents.
and it worked fine in ut 1.8.1
Offline
Klaus_1250 wrote:
New alpha!
Nice :-) I was wondering when the next alpha's/beta's would be comming.
The main change is that uTP (UDP torrenting) is added and enabled by default.
Confused. What is that supposed to be? UDP tracker capability, UDP hole punching or ...? Where is more info?
It also has real-time transfer rate control and latency minimization.
Same here, more info please. Both can mean a lot of things.
Sidenote; I didn't see any options in the Advanced Settings to control these functions.
What is not in 1.9:
UDP hole punching (yet?)
UDP tracker
What is in 1.9:
uTP, the micro transport protocol. This UDP-based reliable transport is designed to minimize latency, but still maximize bandwidth when the latency is not excessive. We use this for communication between peers instead of TCP, if both sides support it. In addition, we use information from this transport, if active, to control the transfer rate of TCP connections. This means uTorrent, when using uTP, should not kill your net connection - even if you do not set any rate limits.
What was in 1.8.1:
uTP, but connection attempts were not initiated by default, and there was no control over TCP as described above. You can enable it, but likely you will see the uTP connections not transfering much data, because they are pushed out of the way by TCP.
What this means for rate control:
You are still free to set rate limits and use external limiters. The "Automatic upload rate" control is flawed enough for most people that it will likely be removed once uTP is well tested and deployed, since it entirely supercedes that feature.
Offline
Alpha-Toxic wrote:
alus wrote:
Fixed, thanks!
Just in case, as this _may_ be a different bug (it doesn't crash for me)
1.9
http://store.picbg.net/thumb/7F/14/459182bd9bff7f14.png http://store.picbg.net/thumb/89/E2/5c9531d1a4d189e2.png
1.8.1 , same torrent
http://store.picbg.net/thumb/DF/7A/ab877bae8307df7a.png http://store.picbg.net/thumb/3D/BB/bf99b6757b513dbb.png
Same bug, it just happened to not crash. This is fixed.
Offline
Well, from the first glance, it doesn't seem to work OK. As soon as I start downloading something, upload performance drops like brick in a vacuum. With 1.8.1 I can upload 145KB/s and download 700KB/s, 1.9 falls to 40KB/s at a 200KB/s download Using mostl uTP connections to uT and BT). Looking at the internal graph, the upload mirrors the download. But I can't tell whether this is 1.9 or the uTP-implmentation in uT1.8.1/BT6.1.1.
[edit]just tested 1.9 with UDP connections blocked. 900KB/s down (limited) and 130KB/s up. Seems it fixes a bug in 1.8.1 as well, where uTorrent had difficulty connecting and uploading to certain peers[/edit]
Last edited by Klaus_1250 (2008-11-26 16:12:00)
Offline