Page 1 of 1

[solved] Download Speed-Indicator not working correctly anymore in 0.6.2

Posted: June 3rd, 2011, 5:47 am
by guru1968
since 0.6.2 the speed-indicator isn't working correctly:

it most of the time shows "0 KB/s" whilst sabnzbd is downloading at full speed as far as I can tell...
- never got that problem with an pre-0.6 version, must have been introduced in the 0.6.x development line!


well, forget what I said...
It was because most of the articles where missing - that caused the corrupted speed-display
-- couldn't that been taken into account when calculating the speed??
it seems that the time needed to find a valid article is considered in that formula...

Re: [solved] Download Speed-Indicator not working correctly anymore in 0.6.2

Posted: June 3rd, 2011, 6:48 am
by shypike
The speed is the average amount of bytes coming in.
For missing articles that amount is very small.
We had 0.5.x file lots of warnings for missing articles,
0.6.x. just summarizes at the end of the download.

I have told this before to others.
SABnzbd is an automation tool, it not geared to people wanting instant interactive feedback.

Re: [solved] Download Speed-Indicator not working correctly anymore in 0.6.2

Posted: June 4th, 2011, 5:53 pm
by guru1968
but one too-old download slows down the complete queue, that's not good...

there is no feedback to the user of this - from the interface such a bad download looks like a normal one: the progress bar fills normally, only the speed-indicator shows very slow rates, that's all
...and finally--that is AFTER 'completing' the download--it tells you that the download failed ("maybe it's too old") :-(

could there not be at least some sort of immediate feedback so that such inclomplete downloads could be cancelled in time?
-- e.g. as soon as the amount of missing articles for one download is too high--so it's obvious that this download never will make it--make the progress-bar red or show an alert-icon next to it with a nice mouse-over detailed explanation or even cancel the download automatically...

(the PAR files typically cover no more than 10% -- so if the missing articles hit let's say 15% (of the totaly amount of articles, of course) already in an early stage of the download, there's no way those gaps could ever be filled by the par set...)