Page 1 of 1
Bandwidth Limit
Posted: July 23rd, 2010, 4:06 pm
by cman675
For people with caps, I would love to have the ability to use a daily limit of how much bandwidth Sab could use. For example, set a limit of 8 gb a day (or even weekly or even monthly), after that it will pause until the next day. My main reason for wanting this is with all of the great automated services that users have created (such as couch potato and sickbeard), while away, my downloads could go absolutely crazy. It would be nice to be able to know that they would be limited. Thanks!
Re: Bandwidth Limit
Posted: July 31st, 2010, 9:46 pm
by jstarship
I second this feature suggestion. It would be nice if this would be implemented in the near future though.
Re: Bandwidth Limit
Posted: August 13th, 2010, 8:04 am
by shypike
It may, but it's not "bandwidth".
You asking for a limit on the amount of downloaded bytes, something quite different.
Re: Bandwidth Limit
Posted: August 17th, 2010, 6:05 pm
by cman675
yeah, my bad. Would it be able to implemented in the scheduler? So not only a time scheduler, but a bytes scheduler? It seems as though something like that would be somewhat simple, given that the history is saved already, and if that is the case, i would be willing to try on my own if pointed in the right direction by someone. Thanks!
Re: Bandwidth Limit
Posted: August 18th, 2010, 2:00 am
by shypike
Work has been done for 0.6.0 to improve byte counting (today, this week, this month, overall, per server).
I'll see if we can add some quota support.
The only thing is that it might make the UI over-complicated,
because obviously everyone will have his/her own quota preferences.
Re: Bandwidth Limit
Posted: August 18th, 2010, 2:16 am
by rascalli
Would it be an option to make a sort of PLUGIN SYSTEM ?
So that you can choose what extra features you would like to install.
For example have a look at
rutorrent for plugin examples
Re: Bandwidth Limit
Posted: August 18th, 2010, 5:20 am
by shypike
We are considering it, but it's a an awful lot of work.
Especially because it also needs ample documentation.
The biggest issue will actually be the never-ending support calls.
Guess who will first one to get the complaints when a plugin fails...