rafi

k, thanks. So , in fact, issue like the incorrect download limit issue that was in 1.9, is now effecting 1.8.3 as well ? cause I was thinking to revert to 1.83 if this was fixed in there...

Firon, what does "outgoing" uTP mean ? Initiating uTP connections ( like 1.9) ? or just being able to respond with uTP to uTP requests.

DWK, is 1.8.3 like 1.9 now ? initiating uTP connections ?

I'm not sure if some of it is not just - uT trying to calculate more correctly you overhead. You can try disable this by net.calc_overhead-false and see the effect

-deleted-

I guess he likes you to migrate to the 1.9 thread with this news bulletin ...

when you guys "minimize to tray" and reopen uTorrent - doesn't it deallocate/reset the memory usage ? (it does so in 1.9 ...)

here is the way I've noticed it's behaving with memory deallocation. Maybe it should be that way in Windows though... I have 2 torrents, stopped. Windows' task manager is used to measure the memory allocated. peers tab is in view. - I run uTorrent and it have ~4.5M usage (all stopped) - I start the two torrents and get to 100 connections @ ~14M (either bt.tranp_disposition = 5 or 10 ) - now I stop the two torrents. Nothing is changed much. still ~14M. Also if I close to tray and re-open it - no change. - next I just MINIMIZE it to the task bar. It drops immediately to ~3M - I re-open the uT window - it's ~4.5M again .... It's not leaking , but I wonder - should it only deallocate memory upon minimizing ? ... may be due to the way Windows manages it's memory ?...

@Richard Choi : you might want to have a look in here: http://forum.utorrent.com/viewtopic.php?pid=397379#p397379 maybe some other configuration item is effecting

yes, 1.8.2 was the previous one

as Richard mentioned - there are new icons here, so the old icon files - are not compatible to this version. Though, I would have tried to find a way to make uT just use whatever icons he can from the old release, and set just the new ones, that are missing) to default in sake of backward compatibility, and also in 1.9

can you please add to the issue of the download limit - another one: Upload data rate is a bit OVER the upload limit. Not by much, but on a 20K UL line with 13K limit the extra 2-4K are important... not sure if it's ~+2-4K or ~+10% though ...

menu - advanced->bandwidth allocation seems to have very little effect (if at all) in this release (uTP+TCP|255) two torrents with the same # peers/seeds (~120 connected for each) seems to get an even DL speed even if one is defined with high bandwidth allocation and the other - low. Both are multi-files torrents all set to "normal" priority

cause it's a smaller program ?...

this is no excuse ... as the sole client suitable for W98 you should be faithful to your 98 remaining believers

so , the 1.8 one is the "good" one when you run 1.9 with it ?

Neronut , why don't you send/post for the devs those two sets of your dat files so they can analyze the differences ?

Pe1XseL: http://forum.utorrent.com/viewtopic.php?pid=396651#p396651 both should work

I see now many more none uTP peers connected (non uT clients). Maybe another bug was fixed on the way (like not connecting in TCP after uTP failed...) ... Also some of the 1.8.2/1 clients are being connected with TCP and not uTP which is a bit strange. The bug of not abiding to a DL limit (for torrents with many seeds) is still there, though it reaches to closer - to about 80% of the limit (with ~250 connected peers). Also the RSS bug of clearing of the main view when executing download on a release is still here... (Richard is aware of that) This release looks much more responsive! it reaches a bit higher DL speed values faster, seems to connect to more peers (as I said, none uTP) and can faster and more easily max my connection DL bandwidth PS: I suggest to expand on the the 5-10-255 options list that is on the first post with the above details ...

there is no real problem for your ISP to detect your protocol and throttle P2P only. so not doing so for ftp is just as expected...

I guess, you tried full encryption ? My guess is that you cannot avoid being detected if you ISP is "good"... does it happen also with a good test torrent like openoffice ? http://borft.student.utwente.nl/~adrian/torrentphp/torrent.php/OOo_3.0.1_Win32Intel_install_en-US.exe.torrent

I give up... why is it so important ? do you really believe your ISP will not throttle you if you use only uTP ? remember that communication with trackers will probably remain as is - TCP. Also incoming connection requests from other clients will be TCP even is they are ignored.

I guess TCP is still used for DHT and maybe also Peer EXchange. Try disabling both and see if you still monitor TCP .

Preferences > Advanced, set bt.transp_disposition to: 5 Edit: Bug(?): bandwidth allocation seems to have no or little effect when uTP is used. FYI, devs.

no, it effects the whole ability to connect outside (if uT is completely blocked) or be connected from the outside . Eventually it will not upload/download since no connections will be made. you should see a failed network status sign on the status bar. If the FW blocks only incoming connections you can probably expect less peers connecting to you, thus slower speed, but I don't think necessarily a dramatic one.