SABnzbd Forums

SABnzbd 0.8.0 beta 1
Windows 7 Pro 32
smpl skin

Thanks for the new version of SABnzbd.

Speed limit scheduling appears not to have any effect in version 0.8.0 beta 1. After upgrading from 0.7.20 the scheduled speedlimit setting was changed in the configuration screen from 300 (= 300 kB/s) to 300%. Setting a new schedule to 30% is accepted but it has no effect. Manual setting to a value, for instance to 300 also does not limit the download speed. Manual setting to a percentage is not accepted.

Erik

Update
The following was shown in the status screen when a speed limit was scheduled:

2015-09-19 10:00:00,006 WARNING: You must set a maximum bandwidth before you can set a bandwidth limit

I had not set the option Status - General - Tuning - Maximum line speed. After setting it to my line speed, limiting the download speed by setting a percentage works. Setting an actual value as with previous versions of SABnzbd does not work.

We'll check.

As you already noticed, only percentages from now on!

safihre wrote:As you already noticed, only percentages from now on!

what's the rationale for this? It's a bit unhelpful!

I would suspect that most people dont care about the maximum, but want to set a rate that they can work out the impact of. For example, i have FTTC and so my line speed is something like 70Mbps. So I know that downloading at 1MBps is not going to impact me watching netflix, regardless of whether the line resyncs at a slightly lower speed or not, so i set it to unlimited at night and 1MBps during the day.

Now I have to "fudge" it by setting max speed to 100Mbps and putting in a percentage to get the same result - but if for some reason my line is upgraded and i get exceed this SAB won't take advantage of the maximum capacity available.

I'll see if we can support existing absolute numbers.

Having ONLY the option for percentage is not a good user experience. The old KB/s limiter should be brought back, at least as an either/or option.

Beta2 will now accept a percentage and an absolute number (with KMG notation).
Still no full backward compatibility because the previous versions used a rather awkward convention of KBps.
So 10 meant 10.000 bytes/sec
We drop that, people will have to review their schedules.

Thanks, that should work well! Looking forward to it!

i have to agree that this is a very un-intuitive way of handling this. I hope to see an additional option to be able to provide a number in (KMG) notation for the maximum bw.

Edit, I'm running 0.8 beta1, just realised that this was announced for beta2. Thank you.

So it seems that KMG schdules have returned at some time and now work in RC1?

Yes, somewhere after beta 2