Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 22823 ideas, 138726 comments, 2639112 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #15556: Transmission should support bandwidth throttling and torrent scheduling

Written by amar.kamat the 12 Nov 08 at 20:47. Related project: Transmission. Status: New
Rationale
Transmission should support bandwidth throttling as it helps manage multiple applications that are bandwidth hungry. Also it would be nice if transmission starts supporting priorities where I can specify a priority level for each torrent and it schedules torrents based on the priority. This will save us from manually scheduling (pausing+start). One benefit will be that transmission might pick up a torrent of lower priority if all high ones are unavailable and hence something or the other is downloaded.

19
votes
up equal down
Solution #1: Auto-generated solution of idea #15556
Written by amar.kamat the 12 Nov 08 at 20:47.
Ubuntu Brainstorm was updated in January 2009. Since the idea #15556 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!
0
votes
up equal down
Solution #2: add label/category driven bandwidth scheduling
Written by aaronp the 30 May 10 at 08:05.
Allow torrents to be labelled and/or categorised and have bandwidth restriction schedules apply differently to each label or category.
This could be as simple as have a 'peak' and 'off peak' schedules in place and then being able to categorise each torrent as either 'peak', 'off-peak' or 'unrestricted'. During peak time when adding or changing a torrent to 'off peak' it was stay paused or restricted. When off-peak time comes around, any 'off peak' torrents would start and download according to the relevant bandwidth restriction until the end of off-peak time at which point they pause again.
Conversely, adding an item with 'peak' category would work the same but during peak time and not off-peak time.
Furthermore, the unrestricted category would be treated as 'peak' in peak time and 'off peak' in off peak time.

This is the simple implementation, a further step would be to allow custom labels set up by the user (i.e. don't restrict just to peak and off peak) and for each label, a custom bandwidth schedule can be set.

Propose your solution

Attachments
No attachments.


Duplicates


Comments
Eldmannen wrote on the 12 Nov 08 at 21:27
I would rather like to see a system-wide interface for bandwidth prioritization that can perform QoS / bandwidth prioritization based on port, protocol or application.

This would make so you can lower prioritize applications such as BitTorrent, and raise the priority of SSH, IRC and telnet. This allows your torrents to go at full-speed, then get automatically throttled on-demand to keep other more important network flow (such as SSH, IRC, web browsing) as fast they normally would run.

rouge568 wrote on the 13 Nov 08 at 02:07
You can already do both in Transmission.

MighMoS wrote on the 13 Nov 08 at 16:52
It does.

charles wrote on the 27 Jul 09 at 20:44
> Transmission should support bandwidth throttling as it helps manage multiple applications that are bandwidth hungry.

Speed limits have been supported in Transmission forever.
Off-hour speed limits were added in 1.40:
http://trac.transmissionbt.com/ticket/964

> Also it would be nice if transmission starts supporting priorities where I can specify a priority level for each torrent and it schedules torrents based on the priority.

per-torrent priorities were added in 1.60:
http://trac.transmissionbt.com/ticket/1943

jrimbo wrote on the 2 Nov 09 at 02:17
Hi Charles,

Although the speed limits is available in Transmission, but we can't really control the throttle. I have cable internet at home with downloads up to 8Mbps, but uploads is only 128kbps.

When I download torrents using Transmission, even by shaping the uploads to 2kbps for example, the real uploads is actually using the whole upload bandwidth. I am assuming this is because it needs to connect to the trackers. You can monitor this from the network monitor in Ubuntu.

I literally cannot browse any website until I pause or exit from Transmission.


Post your comment