Archived

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

Firon

µTorrent 1.9 alpha 15380

Recommended Posts

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.

Download here: http://download.utorrent.com/beta/utorrent-1.9-alpha-15380.upx.exe

-- 2009-05-05: Version 1.9 (build 15380)

- Change: rss.feed_as_default_label controls whether a torrent added from a feed is given the feed's name as a label

- Fix: uTP packet size fix. Sometimes it would send packets exceeding MTU. Fixes long standing rate oscillations.

- Fix: fixed crash when receiving a malformed PEX message

- Fix: evades potential crash when reporting crashdumps

- Fix: crash when parsing some magnet uri components without values

- Fix: crash when starting a torrent in super seed mode and connecting to peers before it's completely loaded

- Change: Installer UI checkbox whether to install or run standalone

- Change: Left align numeric fields in settings

- Fix: Remember category list selection after adding a torrent

- Change: Disabled feed icon has precedence over broken feed icon

- Fix: DHT bootstrap failures now have an exponential back-off

-- 2009-04-1: Version 1.9 (build 14981)

- Fix: uTP would not ramp up its rate fast enough

- Change: .torrent association not a factor in displaying the installer

- Fix: remove file association registry keys on uninstall

- Fix: invalid encoding of non-ascii urls in web seeds

- Fix: uTP fix when receiving acks for old packets

- Fix: uTP variable packet size bug

- Change: link to EULA in installer

- Change: added knob to set the uTP target delay (adjusts how hard to push uTP uploads)

- Fix: don't wait indefinitely for trackers and UPnP when shutting down (two new advanced options)

-- 2009-03-24: Version 1.9 (build 14908)

- Fix: fixed bug where uTP might send packets larger than the MTU

- Fix: fixed inaccuracy in net.calc_overhead

- Fix: download rate limiter for uTP connections

- Fix: lowered uTP overhead by increasing the max packet size to fit mtu

- Change: Enable DEP Compatibility and Image Randomization

- Fix: default download folder was not used when using the WebUI

- Fix: improve TCP/uTP mixed mode

- Fix: removed limit of 100 running torrents

- Change: support some older skins

- Fix: .dat file memory leak

- Fix: Torrent create bug introduced while optimizing file order

- Fix: uTP selective ack was broken

- Fix: uTP bug introduced while lowering overhead

- Change: Preserve file order text

- Fix: Prompt for .torrent association with new installs

- Change: Default bt.graceful_shutdown=true and diskio.no_zero=true

- Fix: Integrity check .dat files after saving. Do not overwrite file.dat.old with a bad file.dat

-- 2009-02-25: Version 1.9 (build 14659)

- Change: uTP variable packet sizes (decreases overhead)

- Change: added code for handing bundles with the bundle type encoded in the bundle

- Change: modified the bundle code to unconditionally pop up dialog box

- Change: modified installer to remove the extra 32 bytes for the bundle type when installing from bundle

- Change: added checkbox to the build torrent dialog so the user has the option not to rearrange the file order.

- Change: Modified the string for the "Start Seeding" checkbox to use 't' as the shortcut since 's' was being used by "Create and Save As..."

- Change: lengthen "About" dialog

- Fix: no longer shows "make this your default .torrent handler" when running a bundle

-- 2009-02-13: Version 1.9 (build 14589)

- Change: optimize torrent generator to move the largest file to the front of the torrent

- Change: support TB, PB, and EB sizes in UI

- Feature: language selector and downloader before installer

- Change: show revision number in HTTP user agent

--- 2009-02-04: Version 1.9 (build 14470)

- Feature: url bundling (from 1.8.2)

- Fix: duplicate search engines are no longer added to the list

- Fix: don't process SYN packets on existing uTP connections

- Fix: uTP congestion control fix

- Change: Translation initialization

- Change: 'h' peer flag for connections via hole-punching

--- 2008-12-24: Version 1.9 (build 13910)

- Fix: never 'upload_only' in superseeding mode

- Fix: total download byte counters

--- 2008-12-20: Version 1.9 (build 13885)

- Feature: NAT hole-punching (for uTP only)

- Feature: account for uTP overhead when net.calc_overhead is true

- Feature: Open URL in Browser for torrents

- Feature: Right click menu in RSS history

- Change: default net.calc_overhead to true

- Change: Red RSS icon for broken feeds

- Change: Bring back RSS icons for new and previously downloaded items

- Change: Use feed name as label to torrents downloaded via RSS

- Change: RSS dialog subscription wording

- Change: URL column in RSS history

- Change: Tweak RSS episode parser to better handle multi-episode feed items

- Fix: uTP compatibility with 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

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 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. In addition we now implement NAT hole-punching for uTP connections, so connectivity should be improved for peers that do not have their ports mapped.

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.

1.8.3 has updated uTP handling code, so it can handle incoming uTP mixed with TCP much better. It is possible to enable outgoing uTP, but it is still not recommended, as the speeds will not be as good as 1.9 will have as we get closer to final.

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, change bt.transp_disposition. This is now a bitfield, so you can add up the following numbers to get your desired setting.

1 - outgoing TCP

2 - outgoing uTP

4 - incoming TCP

8 - incoming uTP

Specific combinations:

255 - both TCP and uTP, incoming + outgoing (future-proof setting, always will mean this)

15 - both TCP and uTP, incoming + outgoing (default)

If you are experiencing slow upload or download performance please try 13911, 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.

Share this post


Link to post
Share on other sites

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?quickkey=ytzgmnwwtwj&thumb=6

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

using the latest alpha and noticed the tracker is stuck at updating.. already restart utorrent, recreate firewall rule and the problem still persist

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

@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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Same bug, it just happened to not crash. This is fixed.

Share this post


Link to post
Share on other sites

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]

Share this post


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