My system gets bogged down big time when sabnzbd is reconstructing files. Anyone throttle that puppy down a bit to keep the rest of the system from bogging down?

 

Here, but it's an ancient article.

https://digiex.net/threads/fine-tune-sabnzbd-to-stop-cpu-hdd-abuse-when-running-other-apps-plex-xbmc.12083/

 

Affected those changes. We'll see if that helps anything.

 

Edited December 7, 20178 yr by dkerlee

7 minutes ago, dkerlee said:

My system gets bogged down big time when sabnzbd is reconstructing files. Anyone throttle that puppy down a bit to keep the rest of the system from bogging down?

 

Here, but it's an ancient article.

https://digiex.net/threads/fine-tune-sabnzbd-to-stop-cpu-hdd-abuse-when-running-other-apps-plex-xbmc.12083/

 

I just use CPU pinning option in the "Extra Parameters" field of my dockers to specifically pin certain cores to certain dockers. This way, no docker, VM or otherwise can lock all of my cores up and affect other systems within my unRaid.

 

"--cpuset-cpus=9,10,11,12,13,25,26,27,28,29" is the command, filling in the cores you want to pin.

maybe try nzbget?  I switched a few months ago and the resource requirement seems a lot lower, and it never locks up like sabnzbd does.

The sabnzbd switches don't work if the Docker container does not have nice, ionice, and the multi-core par2 binary.