SABnzbd Forums

Hi,

Why is the speedlimit now a percentage? I don't see how this improves usability since now it requires the extra setting of the max-speed?
And the confusion with MBit/MByte to add to that.

As a personal note:
Since I am in different places with my laptop the max line speed changes all the time and sometimes I just want it to continue at a specific speed and not have to calculate what 500 or 800kb/s is of the max-speed that I have set?

It's a design choice.
It may not be to your advantage, but it will be to others.
The confusion between bits and bytes is nothing new and is primarily caused by ISPs,
who like to advertise bigger numbers.
(Although for them it's a natural way to express speed, the rest of the IT world is only interested in bytes, not bits.)

I have a bug:

If the speedLimit is set through the API (either with Glitter or Plush), the value on the Config page is not updated while the speed still decreases to the level set with API.
The other way around (updating the value on the config page) does update the value in the API/interface.

The Config pages are not refreshed automatically.
Do you see the correct value after reloading the page?

shypike wrote:The Config pages are not refreshed automatically.
Do you see the correct value after reloading the page?

No, it never gets updated with the value set through the API.
So I can set on config page 50%, go back to Plush/Glitter, set 60% and if I then go back to the config page it will still show 50%. Even though the download-speed is doing the 60% set with the API!
This is not just in Glitter, also in Plush, so you could just test it ;-)

The behaviour has been this way since the API function was introduced, it's a temporary override.
You can discuss the merits, of course.

If you want a permanent change, you need this call:

Aaah, that explains!