Depending on what you're trying to accomplish personally I don't see the point in pinning docker to any given cores, and would rather prioritize one over the other so that any given container can use what it wants unless the priority container wants them

Sent from my NSA monitored device

Well When I have a intensive task like 150mb/s write, or a parity check, my dockers are not responding. I found that by isolating core I do not have this issue (i7-7700). I was thinking that is I did not pin dockers to core, they would use full CPU...

 

THanks for your help !

7 hours ago, yendi said:

Well When I have a intensive task like 150mb/s write, or a parity check, my dockers are not responding. I found that by isolating core I do not have this issue (i7-7700). I was thinking that is I did not pin dockers to core, they would use full CPU...

If your are running 6.7.x you could be hitting an issue a number of us have experienced.  When writing to the array, performance of docker, VMs, other writes goes down to the point they stop responding.. 
 

Rolling back to 6.6.7 gets everything working again..

1 hour ago, bytchslappa said:

If your are running 6.7.x you could be hitting an issue a number of us have experienced.  When writing to the array, performance of docker, VMs, other writes goes down to the point they stop responding.. 
 

Rolling back to 6.6.7 gets everything working again..

i think it's the issue i'm facing. I don't like to downgrade so I will wait for a fix. Thanks

On 9/27/2018 at 1:54 PM, Squid said:

Your screenshot shows that unRaid (and docker) will NOT utilize cores 0, 1, 10, 11.  It will use everything else.

 

Isolating = Isolating them from the OS (ie: OS won't use them)

Cleared this all up for me. 

 

Thanks!

This is still not clear for me. Spaceinvader's video shows that you can have unRAID OS pinned on the first core and use plex on the first and second, or more.

 

 

Edited June 5, 20206 yr by Zotarios
Deleted redundant image

5 minutes ago, Zotarios said:

This is still not clear for me. Spaceinvader's video shows that you can have unRAID OS pinned on the first core and use plex on the first and second, or more.

Isolating a core (Settings - CPU Pinning) means that unRaid AND docker containers will not use those cores at all.

 

Docker pinning means that a container(s) will only use those cores which are allocated to it.  BUT, those cores cannot also be isolated.

 

VM pinning - a VM will only use the cores allocated to it.  Generally used with isolation.

On 6/5/2020 at 8:08 AM, Squid said:

Isolating a core (Settings - CPU Pinning) means that unRaid AND docker containers will not use those cores at all.

 

Docker pinning means that a container(s) will only use those cores which are allocated to it.  BUT, those cores cannot also be isolated.

 

VM pinning - a VM will only use the cores allocated to it.  Generally used with isolation.

So i think i understand the above, but I have a question. lets say I have 8 cores and isolate 1 of them and then in a docker I pin the isolated core and 2 other cores, would that mean the docker is always going to have at least the 1 core, but would use the other 2 if available.

Pinning a container to to an isolated core AND non isolated cores would either mean that the container would only execute on either the non isolated OR the isolated.   Not both.

Just now, Squid said:

Pinning a container to to an isolated core AND non isolated cores would either mean that the container would only execute on either the non isolated OR the isolated.   Not both.

ok thanks

 

So, please validate this. I'm running a dedicated game server in a docker container (Valheim). I want it to have exclusive access to one core, so I'm pinning it to the docker, and isolating the core right ?

 

3 hours ago, Sungray said:

So, please validate this. I'm running a dedicated game server in a docker container (Valheim). I want it to have exclusive access to one core, so I'm pinning it to the docker, and isolating the core right ?

Almost.  It'll run on core 0, but will not run on core 8. 

Right. It's a 3700x, so 8 cores/16 threads. This will give the docker full use of the physical core 0 ?

 

 

I suppose this will not work, since it won't have access to HT 8. The only solution seems to be to disable isolated cpu and enable pinning on 0 and 8, but then the system will be able to "steal" the cpu0/ht8. How should I approach this ?

 

Maybe it works different for docker comapred to VMs, and it's not a passthrough but rather a virtual core, and cpu/HT doesn't matter in this case, and I can only assign one CPU or HT if I want to give exclusive access. So yes isolate and pin 0, but the docker can't use two cores, only one ? Is that how you would approach this for a docker game server ?

Edited February 28, 20215 yr by Sungray

If you want a container to use multiple cores, then you can't pin it to the same isolated cores.  Sure the OS will possibly take some cycles on the cores, but since you're not running any VM, the hit would be minimal.  If you really want it to have more or less unhindered access to certain cores, then you pin it to those cores, and then pin every other container to all the cores except for those ones.

OK got it, thanks.

Sorry to rehash this old thread, but with my 14 core CPU, and I wish to have a much better performance from the plex docker, what do/should I need to do for CPU pinning - if at all.

 

Currently, I get the occasional pause from Plex with error saying the source is not fast enough

 

 

Another resurrection. Sorry. 😅

Read the thread, but I do have one question. 

Let's say I have 2 VM's (one for the wife and one for myself) with shared cores (6C/6T). When I isolate the corresponding cores, will they be exclusive to Both of the VM's or just for one? 

On 1/4/2019 at 8:48 PM, Squid said:

To be honest,  I argued for when a core is isolated to not allow the GUI to let you select it for a container, as I knew that this question was going to happen over and over again. (which it has). 

 

The issue is that the HELP section of Core Isolation mentions VM AND Dockers and thats what makes this confusing.

I Isolated bunch of cores for VM and gave some of them to Dockers, but then community application said it will only use a SINGLE core if i give Dockers isolated cores.

So you see where the confusion is? The Core Isolation Help specifically mentions dockers.

 

Now after i know all of the above, i think the word Docker should be deleted from core isolation Help section.

On 1/10/2023 at 11:27 PM, XisoP said:

Another resurrection. Sorry. 😅

Read the thread, but I do have one question. 

Let's say I have 2 VM's (one for the wife and one for myself) with shared cores (6C/6T). When I isolate the corresponding cores, will they be exclusive to Both of the VM's or just for one? 

 

If you run both VMs at same time you better split the cores 50/50

Otherwise there is no point in core isolation since both use them.

7 hours ago, Hexenhammer said:

 

If you run both VMs at same time you better split the cores 50/50

Otherwise there is no point in core isolation since both use them.

That's not really an issue in my case. Yes, the VM's share the cores and are running in parallel but we actually don't use them at the same time.

Edited January 18, 20233 yr by XisoP

On 1/18/2023 at 9:44 AM, XisoP said:

That's not really an issue in my case. Yes, the VM's share the cores and are running in parallel but we actually don't use them at the same time.

well to replay your original answer, they wont be used by unRaid and plugins.

It will be "exclusive" for all running VMs, if you pin them

you need to both isolate and pin them in the VM settings