Feature #1374

Minimum bytes/second as a trigger for a scheduler item

Added by drbits almost 11 years ago. Updated over 10 years ago.

Status:NewStart date:03/03/2010
Priority:NormalDue date:
Assignee:-% Done:


Category:AddonEstimated time:2.00 hours
Target version:040 - FarfarAway


In scheduler, after "time" line add an additional condition KB/sec < [ ]
The default would be -1 (any speed).
The Bytes would be measured for 60 seconds and the mean compared to the value provided.

This would take care of requests for reconnection on a minimum speed (check every 10 minutes for speed less than minimum). It would also help deal with the Premium Rapidshare over limit problem (speed of download slows immensely).

Refer to
Issue #876, Issue #1258,

Note: Even with the new longer measuring time, I am still seeing swings from near 0 to near 200 bytes per second (due in my case to processor load or memory paging). Some longer measure must be used (at least 60 seconds). Since the scheduler cannot be set more precisely than 60 seconds, that seems the ideal measuring time (we don't want overlapping measurements, one measurement starting on the minute can serve all).

Related issues

Related to Feature #876: Addon: DownloadRestarter New 11/05/2009
Related to Feature #1258: Minimum time between automatic reconnects New 02/08/2010
Related to Feature #1605: Grouping: Next Scheduler Features and related issues New 04/16/2010
Duplicated by Feature #310: Add 2 new scheduler events New 08/16/2009

Also available in: Atom PDF