Transmission does not favour upload limits

[krx]

Hi,

I have been using transmission for some time (since maybe 1.3x) and congratulate you on steady and good work[[BR]] I would like to report bug, which is in 1.50 version. When using:

1. Transmission 1.50
   instaled as opt-ware from NSLUG repository, on USB stick.
2. on Asus WL-500G Premium V2
   
3. F/W DD-WRT v24-sp2 (01/01/09) mega (SVN revision 11296M NEWD Eko)
   

Transmission does not favour upload limit. Uplink is 768 Kbps, ~93 KB/s, I set Transmission to say 70/50/30 KB/s, is still hogs-down all uplink (~85-95 KB/s, when summed from transmission-remote -l "Up" column), and router start to loose/delay packets (for example pinging ISP router goes from 10 ms, to ~350 ms with packet losses). I can either use transmission, or everything else but it ;-)

Config is ass follows:

{
    "blocklist-enabled": 1,
    "open-file-limit": 60,
    "preallocation": 2,
    "download-dir": "/mmc/transmission/downloads",
    "download-limit": 100,
    "download-limit-enabled": 1,
    "encryption": 1,
    "lazy-bitfield-enabled": 1,
    "message-level": 2,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 120,
    "peer-port": 51413,
    "peer-port-random-enabled": 0,
    "peer-port-random-low": 1024,
    "peer-port-random-high": 65535,
    "pex-enabled": 1,
    "port-forwarding-enabled": 1,
    "rpc-authentication-required": 0,
    "rpc-enabled": 1,
    "rpc-password": "",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "10.77.77.1",
    "rpc-whitelist-enabled": 0,
    "upload-limit": 30,
    "peer-socket-tos": 8,
    "upload-limit-enabled": 1
    "upload-slots-per-torrent": 10
    "proxy": "",
    "proxy-auth-enabled": 0,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": 0,
    "proxy-port": 8080,
    "proxy-type": 0,
}

[charles]

I set Transmission to say 70/50/30 KB/s

I don't understand what this means

[krx]

Replying to charles:

I set Transmission to say 70/50/30 KB/s

I don't understand what this means

Sorry. This means upload speed limit.

P.S. This bug can be linked with #1832.

[drsassafras]

I don't understand what he said either, but if he is saying transmission does not obey the global upload limit in 1.5, he is right. Mine is set to 40k and uploading at about 60 right now....

I think there was a problem with this that I reported before. It was fixed and worked fine in the last few releases.... Even the 5.0 beta if I remember correctly. Didn't use it all the time though.

Brendan

[krx]

Replying to drsassafras:

I don't understand what he said either, but if he is saying transmission does not obey the global upload limit in 1.5, he is right. Mine is set to 40k and uploading at about 60 right now....

Yes, I meant, that Transmission does not obey global upload limit in 1.50 version.

[charles]

Do you have any per-torrent speed limits set, as well as the global speed limit?

[drsassafras]

one torrent is set to global limit, the other is set to 30kb/s

[krx]

Replying to charles:

Do you have any per-torrent speed limits set, as well as the global speed limit?

I do not gave any speed limit per torrent, only global limit. Until this moment I did even knew, that Transmission had capability to use per-torrent speed limits. I only knew about priorities, which I have used sometimes for select files. As I understand, Bittorrent protocol, it is not advised to set any restrictions/etc., as doing that impacts overall performance of the network, therefore I try to do that as little as possible.

[krx]

I strongly think, that this bug is linked with #1832. I will update, once I have some test results.

[livings124]

From #1832: Transmission now correctly obeys global upload limit negating the #1831 bug.

[drsassafras]

I don't get it. Has the code been fixed for the next release?

[livings124]

drsassafras: If you have a individual limit set, that is not included in the global limit. 40+30 >60. Your results sounds about right.

[drsassafras]

Thanks for explaining this.

In the preference pane, it says "Limit Total Bandwidth" Perhaps that should labeled to something more suiting, as from what you have said, it will not limit the total bandwidth. Or perhaps when using the individual setting (as many users might not ever want to limit an individual torrent.), there could be some indication that it will be in addition to the "limit total bandwidth set in preference pane" Or something like that. I hope I got my idea across.

If one changed "limit total bandwith" to "global speed limit" what % of users would understand that... 3%? 5%? 10%? Somewhere in there I guess. Another wording might be better.

What about the global maximum connections? Can I overtax this by changing the # of connections in the torrent? I guess they should both behave similarly.

Dr. Sassafras