Any way to suspend a docker during a certain action?

[Netbug]

So I've noticed that when my SABnzbd is doing post-download work (decompression), my CPU usage spikes to pretty much 100% on all cores. This is causing freezing on any stream I'm watching.

 

Is there any way to set the docker running SABnzbd to wait until there is no/little activity on the other dockers? Or, if that's not possible to automatically limit it to run at certain times (say 2300-1100) unless manually triggered to limit the impact?

 

Dockers: binhex-sabnzbd, PlexMediaServer, binhex-radarr, binhex-sonarr, EmbyServer

[itimpi]

Why not simply limit the cores the docker is allowed to use?

[Squid]

10 minutes ago, Netbug said:

docker running SABnzbd to wait until there is no/little activity on the other dockers?

https://forums.unraid.net/topic/57181-docker-faq/page/2/?tab=comments#comment-566087

 

[Netbug]

10 minutes ago, itimpi said:

Why not simply limit the cores the docker is allowed to use?

I thought of that, but there are a lot of times when we're not streaming and there can be quite a backlog of stuff, so I think it would work, but much less efficient.

[Netbug]

4 minutes ago, Squid said:

https://forums.unraid.net/topic/57181-docker-faq/page/2/?tab=comments#comment-566087

 

This looks like exactly what I'm trying to do.

 

So just to be clear, I could set the "Extra Parameters" of the binhex-sabnzbd in the "Advanced" view to "--cpu-shares=2" and that would limit that docker to only use 2 cores when other cores are in use. Is that correct?

[itimpi]

1 minute ago, Netbug said:

This looks like exactly what I'm trying to do.

 

So just to be clear, I could set the "Extra Parameters" of the binhex-sabnzbd in the "Advanced" view to "--cpu-shares=2" and that would limit that docker to only use 2 cores when other cores are in use. Is that correct?

The way to do this is to go into Edit mode on the docker and then switch to Advanced view  (at top right) to see the options for pinning the container to running only on specific CPUs

[Squid]

Not exactly.

 

You wanted to limit CPU resources of SAB when other docker apps want / need them.  

 

That setting sets Sab to be the absolute lowest priority of any given docker container.  Such that every container has priority over it (default cpu shares setting is 1024)

 

Sab can still use all the cores, but it runs at such a low priority when say Plex requires them that it shouldn't make a huge dent.

[Squid]

@itimpi and myself ( @Squid ) are giving two possible solutions.  Either via pinning cores or dynamically via cpu-shares.  They are not the same solution.

[Netbug]

Wonderful. Thank you folks. I will play around with it and see how it goes.

[ArdNsc]

On 2/22/2020 at 2:48 PM, Squid said:

That setting sets Sab to be the absolute lowest priority of any given docker container.  Such that every container has priority over it (default cpu shares setting is 512)

I have been experimenting with "--cpu-shares" and it does not what I am intending to do. I read everywhere that the default value is 1024, are you sure it's 512? Is this some kind of special setting in unRaid or just a typo?

[Squid]

2 hours ago, ArdNsc said:

typo?

this