Transmission not respecting download speed

transmission app is not respecting download speed manually set to anything above 10MBps. If I put in 40MBps or 120MBps it always only does 10MBps which is the highest built in setting.

How can we fix this?

BUMP Still an issue and I have found no workaround besides setting speed limits for the device on the router. Unlimited speed is causing network instability as it even stomps out DHCP during a modem reboot. Maybe I have to run this in a debian VM also…

Transmission also stomps out sonarr and radarr and prowlarr…

qBittorrent is a better client.

Transmission doesn’t use async disk io, causing the gui to lag during high network/disk activity and slower startup. It’s a shame because the progressive loading of the initial state and updates in the web-ui makes it usable at >200k torrents – though then you run into another issue where the announce rate isn’t fast enough to complete all announces before they ‘expire’, and since it’s not user-configurable you need to modify and build from source to increase it. When I tested with ~250,000 torrents, it also literally took hours to start up.

qBit, on the other hand… The backend handles >200k torrents just fine and still starts up in less than a minute (use sqlite resume data), but the webui crumbles without heavy use of filters since it loads the initial state in on gigantic json. However, disk io is async, it has more features, faster startup, and a much better API for scripting. Whodathunk that software for reading/writing from disks would work better if disk activity is separate from the main thread…

Probably not the solution you’re looking for, but I’ve abused every client and while they all have their flaws – I’m confident that qbit is the best option overall.

2 Likes

Ok, I will give it a go thanks for the advise.

I think you’ll like it better once you get used to it. There are two builds of qbit, one with libtorrent 1.2 and the other with libtorrent 2.0. A lot of people seem to prefer 1.2.

A couple configuration changes I recommend are to use the sqlite database for resume data, and set the cache to be managed by the OS.

If you run into any issues, post them up here.

I forget the setting’s default, but for ZFS (TrueNAS), you’ll also want to disable “Pre-allocate disk space for all files”.

1 Like