Archived

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

Firon

µTorrent 1.9 alpha 15380

Recommended Posts

@DreadWingKnight: net.calc_overhead = true

@Switeck: So I am really that unfortunate to have 20:1 dl/ul speed from ISP, and this is the overhead? If that's the case I can't really seed before downloading the complete torrent first, is it?

Share this post


Link to post
Share on other sites

That 20:1 ratio is not a result of your ISP, it's caused by TCP networking overheads and/or other problems! Even the BitTorrent client type (Vuze/Azureus, Deluge, Transmission, BitComet, etc) you're downloading from may be poorly written and increasing the amount of overheads.

Even a "perfect" single TCP seed (or HTTP) connection has worse than a 50:1 download-to-upload ratio from your point of view...meaning that if you're downloading from them at 50 KB/sec then you're using more than 1 KB/sec UPLOAD to continue at that download rate.

uTP connections could potentially increase the DL/UL ratio above 50:1, but probably won't do so by much.

Share this post


Link to post
Share on other sites

I'm getting 12/0.5 Mb/s dl/ul from my ISP, so it's close to the overhead ratio of 20:1 that you've mentioned earlier. That's what I meant, not that it's my ISP fault.

The seeder client was listed as libtorrent 0.11.9, so it seems that + small pieces are the culprit in that case. I never suspected that overhead can reach such values.

Thanks for the info.

Share this post


Link to post
Share on other sites

niksus,

The speed of your line is totally unrelated to TCP overheads. ISPs have just been giving far more download than upload for years, with little reason to change now due to entrenched infrastructures.

Share this post


Link to post
Share on other sites
Switeck:

uTP connections could potentially increase the DL/UL ratio above 50:1, but probably won't do so by much.

I never understood why... in general using UDP should be more efficient then TCP since you can better tailor it to your own application's protocol and should save overhead data.

Share this post


Link to post
Share on other sites

rafi, I mean how fast you download (50 KB/sec)...with a (1 KB/sec) upload speed "cost" for doing so in overheads. You'd want the upload cost to be low for your download speed to be more efficient.

Normally, TCP downloads have about a 50:1 DL:UL ratio at best. uTP connections are very unlikely to increase that over 100:1 but may barely break 50:1.

Share this post


Link to post
Share on other sites

ok, random problem.

Running win 7 RC1 x64, and utorrent 1.8.3 - running the installer to update to this version utorrent-1.9-alpha-15380.upx.exe) seems to do nothing - it stays as version 1.8.3

Share this post


Link to post
Share on other sites

19380 for me aswell as previous beta is not adhering to max upload speeds in the setting or rmb drop list. They are always going faster than set

By faster it's meant to 10 kB/s and more kB/s than set, maxing out bandwidth up/down. Throttling utorrent downloads and slowing considerable other inet softwares running.

Is this corrected for the next beta ?

1.8.2 or 1.8.3 was corrrect. I could use those versions, although nothing is gained by sticking to old versions. In the way of progress for utorrent and feedback for it if everyone used old versions.

Just a quick update, if have just one download running and set in setting for one only it remains as should within +1 to 2kB/s. Seeding on/off makes no difference or ihow many seeds in setting set for uploading. Just tried with 1 download only in setting and have tried with another download in paused state and still ok. Not ideal downloading one at a time when plenty of download bandwidth availble for more, but may point you in the right direction to fixing this.

sorry though i was onto something there seems not, but isn't going further than +5kB/s so maybe something ? Though still more than set, let's see what you find for next version for us to try.

Keep up the good work :)

Share this post


Link to post
Share on other sites

Same problem here, running Windows 7 x64 RC Build 7100 and it wouldn't let me upgrade to 1.9 from 1.8.1 or 1.8.3. I had to uninstall first then install 1.9.

Share this post


Link to post
Share on other sites
Is this problem specific to Windows 7 64? Has anyone gotten the installer to work properly using regular Windows 7?

A fresh install works fine on Windows 7, I think its upgrading from an older version that doesn't work properly.

Share this post


Link to post
Share on other sites
I never understood why... in general using UDP should be more efficient then TCP since you can better tailor it to your own application's protocol and should save overhead data.

UDP is an unthrottled, connection-less protocol. Usually UDP is used for streaming video or audio, high bandwidth applications where when bits are lost people would not notice. Essentially your computer just spits out data and "hopes" that it reaches it's destination. Because Torrenting/uTorrent in nature automatically ensure that all data is received, using UDP is not a problem. UDP will make better use of bandwidth because handshaking does not occur, thus less overhead. Also, in TCP it is possible that clients can tell other clients to "slow down" if they are outputting too much data for the network. Thus why TCP is said to be throttled. In UDP there is no throttling, all clients can output as much as data as they want, as fast as they want, into the network.

Share this post


Link to post
Share on other sites

Just wondering if this correct with v1.9 build15380 that with 1 torent active that is seeded. Someone is uploading while at same time, downloading betwen 5 - 10 kB/s. This is over many minutes, question is why download at that many kB/s when the torrent is 100% and seeding ?

I have stopped that torrent for now to see what you say here. Maybe i'm giving away more than torrent data for which they're downloading from me ?

Or is this normal !! I don't ever recall having this seen before of many years, running various torrent softwares.

Share this post


Link to post
Share on other sites

Those other torrent programs have certainly not shown the probable download "costs" for uploading quickly.

Share this post


Link to post
Share on other sites

Neither has utorrent ever before shown the same costs. First time i have seen this happen, here's how to invoke it, and fix it?

Bandwidth - Alternate upload rate when not downloading (kB/s): - tick - 0

To stop it downloading higer rates (why should it the torrent is seeding) - put a figure in the box of yor max upload rate.

I have the same speed speed of without - 0 - i the box and with a figure as with a - 0

Just now i down have higher download leech out, heck knows what they were downloading.

Max download on the seed now is 0.1 - 2.0 kB/s and never any more as was as writen above.

Share this post


Link to post
Share on other sites

Or, you could just set net.calc_overhead to FALSE! (it's in advanced settings)

But then you're only HIDING the real amount of download used...which is probably LOWER than what other BitTorrent clients actually use while uploading at the same speed.

Share this post


Link to post
Share on other sites

Sorry if hoped on any devs sensitive coding, no idea that it would of been. Think of this then more of what shouldn't be done, if the lable doesn't say auto 0 it means just that.

No i'll leave it as is now, just won't set to 0 again for that one. Tried 0 for auto, though it didn't say it would be auto. So far back to normal never gone over 2.0kB/s since, as far as i can tell.

SET net.calc_overhead to FALSE - I have it set as TRUE, which is the way i would prefer it to be. Thanks for pointing this out.

btw: I'm still interested to know what it would have been download at 5- kB/s, it was a seeded file already finished (no more download needed).

Share this post


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