Throttle download speed

[ciotorcristian]

Is your feature request related to a problem? Please describe.
Would it be possible to implement a feature that limits the download speed whenever a Jellyfin stream begins?

Describe the solution you'd like
Perhaps there could be an option to specify what you want to throttle—a flag allowing users to choose between limiting both download and upload speeds or just one of them. This flexibility would provide more tailored control for different scenarios

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[itschasa]

Added in v1.0.0

[ciotorcristian]

Hello,

It is still not working or I am do not have the correct config:

[2025-03-30 21:52:57,939] [INFO] <media_servers> Upload reduction values = http://jellyfin:8096: 14.471 (media_server.py:47)
[2025-03-30 21:52:57,940] [INFO] New calculated upload speed: 85.529MB (main.py:98)
[2025-03-30 21:52:57,940] [INFO] New calculated download speed: 100MB (main.py:99)
[2025-03-30 21:52:57,940] [INFO] Getting active torrent counts (main.py:101)
[2025-03-30 21:52:58,008] [INFO] Set upload speed for http://qbittorrent:8085 to 85.529MB (main.py:123)
[2025-03-30 21:52:58,008] [INFO] Set download speed for http://qbittorrent:8085 to 100.0MB (main.py:124)
[2025-03-30 21:52:58,009] [INFO] Speeds updated (main.py:127)
[2025-03-30 21:52:58,009] [INFO] Waiting for next update event (main.py:134)

==================================================

units: MB
min_upload: 1
max_upload: 100
min_download: 1
max_download: 100
clients:

• type: qbittorrent
  url: http://qbittorrent:8085
  username: admin
  password: QeHNHgBHFw!2Uvuafz
  https_verify: true
  modules:
  media_servers:
  • type: jellyfin
    url: http://jellyfin:8096
    api_key: 978e44f63e93469399782ef0f506ad6b
    https_verify: true
    bandwidth_multiplier: 2
    update_interval: 10
    ignore_local_streams: false
    ignore_paused_after: 300
    schedule:

Could you please help me?

[itschasa]

These logs indicate that it successfully changed the download speed. Did you see the upload speed change? Is it just the download that hasn't updated? If you're viewing in the WebUI, you might need to refresh the page in order to see the change.

[ciotorcristian]

Hi,

The maximum download speed is 100. It calculates the download speed as 100, but it should have been equal to the upload speed. It's not that it does not the speed, it's that the speed calculation is wrong

[itschasa]

Ahh, I see what you mean. I've made it so the media server module does not decrease the download speed, as the media server is uploading, not downloading. My logic is that only the upload would have to be decreased. If you wanted it to have a download reduction as well, I can implement something like that?

[ciotorcristian]

Yes, if you can implement it this way it would be awesome. Maybe a toggle to enable download limiting?

[TimetravelerDD]

so i think the idea here is that downloads in qbittorrent eat up about 3% of the download rate as additional upload for transport overhead

I thought about this too, but it is actually harder to implement as it seems at first glance. speeder would first have to check whether a download is running and how fast. then it should reserve 2-5% of this bandwidth additionally in upload and if it can't (already at the minimum), then it should throttle the download accordingly (to a configurable amount) or maybe decrease the minimum even more, although this should also be user configurable.

Honestly speaking, as much as I though this would be amazing, I am having second thought whether is is worth it or not.

An alternative would be to toggle on "Apply rate limit to transport overhead" in qbittorrent, though my understanding is that this makes the connections less efficient, so it should be only a temporary setting at best.

Personally I would just increase the safety margin a bit and accept that the solution is "only" about 95% accurate ;-)

edit: after some more though I believe the original question may have had a different problem in mind. aside from the bittorrent download overhead, one must also think about plex/jellyfin upload overhead. This is actually way easier to implement: basically it could be a flag or a factor (defaulting to 5% ?) that reduces the download speed by "streaming speed * factor".
Eg. if a 20 MBit Stream starts the upload should be reduced by 30 Mbit (assuming 1,5x bandwidth_multiplier) and download should be reduced by 1 Mbit (based on 5% overhead factor)

In Summary: I would be in favor of implementing the latter while the first problem is too difficult to tackle imho