Mysterious download speed limit

[jp63670]

I just had 2.0 installed and it was mysteriously limiting downloading to 300K. Rebooted my router to be sure there was no problem there. Ran Glasnost to see if there was a new issue with my ISP. In both cases nothing. I uninstalled 2.0 and reinstalled 1.85 and the limit went away. Back to downlaoding at 1MB.

[isolated]

Similar problem here - download speed dropped after update without any change in settings. Reinstalled 1.85 and back to normal.

[Firon]

Raise your upload cap. 2.0 behaves differently in that it shows you TCP (and uTP) overhead and uses this overhead to calculate how much bandwidth you're really using. As such, the upload limiter really, really sticks to the number you gave it. It will now throttle download (if necessary) if you exceed your upload cap because of overhead. This makes it much, much harder to choke your connection or slow it down just because you're downloading fast.

In other words, that mythical 20-30% reduction in upload cap to account for download overhead isn't necessary anymore.

That being said, the latest 2.0 does seem to have a bug with said throttling when uTP is enabled (it's limiting the download way more than it needs to). So it'll be rectified on the next build.

[Deneteus]

Thanks for mentioning this. I almost blamed Comcast for throttling.

[V@no]

What exactly is uTP and where do I disable it?

cause it's kind of f.up right now...setting upload limit to 60 will limit download rate to 1mb/sec max...

[DutchPunk]

I don't know if this is related to the UTP, but anyway;

I'm running on 1.8.4. without problems with every bitclient - except 2.0

Whenever a peer with 2.0 beta connects to me, the speed goes up & down like a rollercoaster.

As well on my home PC (1Mbit) as the seedbox (100Mbit). Over several trackers.

Within a minute it can swipe all traffic to 0kbps, and goes up to the max after a second of 10.

That lasts a 30 seconds-1 minute before all goes down to 0 again. Ongoing problem untill the 2.0 peer(s) disconnects again. If i ban/filter the IP or stop the torrent in my client, everything is back to normal again. It's a drag, as i constantly have to check which clients connect to me.

I tested it on 3 different (private) trackers, and 2 other persons on 1 of that tracker have the same issues.

I made some screenshots to show what i mean (seedbox WebUI)

20:10h (stopped a torrent with a µtorrent 2.0 peer in swarm)

14 active torrents from 1,3kb/s up to 1MB/s active traffic

20:14h (added a torrent again i was busy on)

There's one µtorrent 2.0 peer on 70,9% and when it connected

all torrents went flat to 0 and lost connection with all swarms

(screenshots available on request for privacy reasons)

[Switeck]

DutchPunk,

Is the uTorrent v2.0 peers/seeds using uTP connections?

Did you try disabling uTP?

Did you try setting bt.tcp_rate_control to false?

[joshuass]

Hey guys. I to am noticing some strange things going on with the caps and download speeds.

Here's what I did for downloading 3 torrents:

Setting download rate to "unlimited" nets me only 40-70KB/sec per torrent.

Setting download rate to "1000kB" nets me 110-150KB/sec per torrent.

Setting download rate to "25000KB" nets me 200+

Every time I adjust the download rate, the upload rate (or perceived rate) increases as well. I saw 70K as a rate even. My connection is a 8mbit/512k cable through Time Warner/Earthlink. The rate was to be limited to 20K (atleast until I can figure out vyatta's qos)...

I'm finding the whole download/upload rate capping to be hard to understand with the 2.0 RC builds. Are my findings similar to whats being said here like I think it is?

[Lord Alderaan]

How is the cap enforced?

Heavy downloading generates upload overhead. Does that upload overhead have to fight with the real uploading over the total available (capped) upload bandwidth, or does the overhead get priority?

Because if the overhead gets priority it shouldn't really lead to slower download speeds. It should lead to lower real uploading speeds. Right?

[DutchPunk]

Switeck,

Is the uTorrent v2.0 peers/seeds using uTP connections?

Some show as µtorrent 2.0, some as µtorrent 2.0 (utp) in my peerslist. So i think both

Did you try disabling uTP?

How/where in 1.8.4

Did you try setting bt.tcp_rate_control to false?

These settings are not available in the Advanced list in Preferences (1.8.4)

It get's noted only in the help section (???)

[Switeck]

I wasn't aware v1.8.4 lacked bt.tcp_rate_control ...oh well, I guess that's why it's not considered latest or supported.

So you have some uTP peers/seeds (usually uTorrent v2.0 clients).

Disable uTP by setting bt.trans_disposition to 5 -- reenable by setting it back to 13 or 15.

[V@no]

Ok, bringing up old topic, because nothing seems to change in latest 2.0.1 version....

[EDIT]

A work around this is to disable net.calc_overhead ? is this correct?

Any plans on actually fix this without sacrifice features?

[Firon]

Raise your upload limit so it's high enough to actually handle the download speed you want, or disable net.calc_overhead.

[V@no]

Well, the thing is, the same exact settings are working fine in pre-2.0 versions (1.8.x).

And yes, net.calc_overhead fixed the problem.

[rafi]

you better set up a bit higher UL limit than change calc_overhead

[V@no]

In my case in order to download at full speed (5mb/sec) I have to remove any kind of limit from upload speed - that is unacceptable. So, for now I have to disable net.calc_overhead

[gurjs]

yea im having this problem too i dont know what it is i get unstable speeds