Hi,
Any way to tell SABnzbd to only process (unpack, unrar, etc) once all queued downloads complete?
During processing my computer only averages 2.0 MB per second while I can max out my connection at 3.7 MB per second while no processing is happening.
Would make a lot more since for me to download everything first and then process.
Thanks,
Will
Only Process After All Downloads Complete?
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Only Process After All Downloads Complete?
On what hardware are you running this? If the par2/unrar has such an impact, I would expect it's lower-spec hardware?
On which OS are you running this? Some remarks below are meant for Linux.
Approach #1: change the priorty
See if setting 'ionice' in the SAB parameters helps. If not, try lowering the priority of par2 / unrar, or of SABnzbd as a whole.
Approach #2: the API programming way: let a script run each minute: move anything in the download-queue with a short ETA (< 3 minutes) to a lower position in the queue (or lower queue priority) *if* there is stuff with longer ETA. The result of this is that big downloads are always on top, and that downloads will only reach unpack / unrar if there is nothing big to download anymore.
Approach #3: another API programming way: only add stuff to the queue in Download-only mode. As soon as the download is complete and it reaches the History queue, and *if* there is nothing else to download, change the option to Unpack/Repair so that SAB puts it again in the queue and starts the unpack/repairt. HOWEVER, SABnzbd seems not to offer to do that last action: once done in History, you seem not to be able to do more processing on it :-(
EDIT: the SAB-API seems to offer a History-Retry option: http://wiki.sabnzbd.org/api#toc43 . That could be interesting: Download-only everything into the queue. Then, each x minutes, let a crontab script check if the Download-Queue is empty, and if so, get something from the History queue that has Downloaded-only, 'retry' it into the Download-queue, and change Download-only to full processing.
EDIT 2: Pity: the Retry-option in the History-overview is only selectable if something went wrong in the download. So not for the above use case #3.
On which OS are you running this? Some remarks below are meant for Linux.
Approach #1: change the priorty
See if setting 'ionice' in the SAB parameters helps. If not, try lowering the priority of par2 / unrar, or of SABnzbd as a whole.
Approach #2: the API programming way: let a script run each minute: move anything in the download-queue with a short ETA (< 3 minutes) to a lower position in the queue (or lower queue priority) *if* there is stuff with longer ETA. The result of this is that big downloads are always on top, and that downloads will only reach unpack / unrar if there is nothing big to download anymore.
Approach #3: another API programming way: only add stuff to the queue in Download-only mode. As soon as the download is complete and it reaches the History queue, and *if* there is nothing else to download, change the option to Unpack/Repair so that SAB puts it again in the queue and starts the unpack/repairt. HOWEVER, SABnzbd seems not to offer to do that last action: once done in History, you seem not to be able to do more processing on it :-(
EDIT: the SAB-API seems to offer a History-Retry option: http://wiki.sabnzbd.org/api#toc43 . That could be interesting: Download-only everything into the queue. Then, each x minutes, let a crontab script check if the Download-Queue is empty, and if so, get something from the History queue that has Downloaded-only, 'retry' it into the Download-queue, and change Download-only to full processing.
EDIT 2: Pity: the Retry-option in the History-overview is only selectable if something went wrong in the download. So not for the above use case #3.
Re: Only Process After All Downloads Complete?
OK approach 1 seems to be working. I have set Nice to "-n 10" and IONice to "-c3 -n5" and seems to work well.