Linit upload slots per torrent - PLEASE!

[Chindokae]

The default setting of 14 upload slots per torrent is just too many for some routers. It is also high enough to trigger traffic shaping on some ISP's because that many upload connections makes it look like you are running a server.

The 14 connections were causing other applications on the same machine and other machines on the same network to be unable to start new connections. The limitation was not coming from my SOHO router - it is a genuine Cisco box and can sustain 1024 outbound connections. I wasn't even getting close to that. (< 50) The limitation is somewhere on my ISP's network, it counts against uploads only, and the only thing I can do about it is learn to live with their limitations.

I am aware of the setting in settings.json (upload-slots-per-torrent) and tried altering that, but found that the client very (un) helpfully rewrites that value to 14 at startup. It even does a chmod on the file if I make it read only.

I finally reduced the number of upload slots to 6 by setting the appropriate variable and building from a tarball, and presto, my network problems disappeared. I was actually able to increase my max upload speed from 250 to 450, so everybody won. This limit wasn't about bandwidth, it was about the number of concurrent upload connections.

Not many users want their torrent client to cause their network to collapse and more ISP's are doing traffic shaping every day.

Virtually every other torrent client provides this functionality. Transmission should too, if it wants to grow its user base.

[Longinus00]

Don't edit settings.json while transmisison is running.

[Chindokae]

I shut it down, edited the file, and started it back up. Same result. It writes the file on startup.