![]() ![]() You should leave core 0 and it's ht core for unraid. I have no issues here on a dual cpu board. I tried CPU pinning cores to the BOINC docker and keeping the BOINC config at 100%, but BOINC still interprets the number of cores from the CPU definition.Īnyone have a better solution that is more portable and less hardcoded to the current system configuration? I don't always run CPU isolation and would like to keep as much as possible immune to my whim to change it. This setting is in: Options->Computing Preferences->Computing->Usage limits->Use at most '50%' of the CPUs. how many are still available for docker allocation. So, in instances where you isolate CPUs away from the host, my workaround is to tell BOINC the percentage of the CPU still available to it (i.e. Probably not the biggest deal, but not ideal as there is still likely overhead switching between them. The result, each core has 2 BOINC threads competing for resources. So, when running the BOINC container and letting it use 100% on my CPU, it spins up 16 WU processes because it thinks it can do that many on the processor concurrently without multitasking on the same core. ![]() For example, my 8C/16T AMD 3800X still reports as such even though only 4C/8T are available for allocation by the host (and by extension, docker). Making the isolcpu system initialization change does not modify how the CPU is reported to the docker process and the containers that are run. I have half my CPU cores available to Unraid and half isolated for VMs. I have not run a CPU taxing container like this before and found an interesting thing that might be applicable to others. I started using this container this week. ![]()
0 Comments
Leave a Reply. |