Problem with window thread scheduler? - Multiple CPUs win10 ONLY uses group0

Software & Operating Systems Windows
#1

Device is a ProLiant DL360 Gen9 -
System ROM P89 v2.80 (10/16/2020) .
CPU x2 Intel(R) Xeon(R) CPU E5-2650L v4 @ 1.70GHz.
RDIMM is 64GB on 4x16gb sticks in sockets 12 and 9 for each processor.

Windows Ver is 21h2 build 19004.1889.

The problem I am having, is Windows seems to ONLY put tasks to Group 0 (Node 0) and will never assign to Group 1 (Node 1) even when a task is running at 100 use for that group and it will continue to only run new tasks in that group forcing me manually move something like folding at home to the other node.

Is there a hardware issue? or is there something in bios that could be creating this behavior?

#2

What version of Windows 10? If I recall correctly, Windows 10 Pro and up only supports 2 CPU’s

Out if interest, why not just run Windows Server?

1 Like
#3

Its W10 Pro.

I have not ran a server OS for windows since like Windows Server 2008 R2 - I tend to use my windows servers as more of a workstation, prior to this I was using this box in a different config as a ESXi host, but I was having issues with the amount of overhead, and lost access to the free esxi licenses when i graduated.

Also in the past I had so many problems with installers hating non-client OS, so I’ve just stuck with Pro version of W10 or W7 or even Linux unless there is a specific need for a feature.

#4

I’ve been running Server 2019 and 2022 on VDI VMs for a while, the only sticking point for me is the lack of a first party photo viewer

Have you tried installing Windows Server and seeing if the CPU’s show up? May be a good test if its not much work

2 Likes
#5

I dont mean to sound silly but are you sure its win10 Pro, and not hime or something.

Pro should support 2 sockets, but anything less than pro will only support 1 which is why i ask.

Or could it be that it is pro but not activated fully? Not sure if/what thats does in realterion to the socket unlocking but just a guess.

2 Likes
#6

If it was home I couldn’t RDP into it, and if it was home Bitlocker wouldn’t work, nor could the device be domain joined.

1 Like
#7

maybe you are missing what I am saying.

The problem I am having, is Windows seems to ONLY put tasks to Group 0 (Node 0) and will never assign to Group 1 (Node 1) even when a task is running at 100 use for that group and it will continue to only run new tasks in that group forcing me manually move something like folding at home to the other node.

Nothing about the CPU not showing up. The both CPUs are there and available in windows for use. If I use BOINC to run WCG or something, I can run all 56 threads concurrently if I take the time to move the threads from group 0 to group 1.

#8

Assuming the memory is set up as NUMA, then some program (for example Paint) could only run on one or the other NUMA-Node. If you wanted both CPUs to work on that one program, you would need to set your system to UMA.

There is also the Windows concept of Processor Groups. You will have to do your own learning there as that is beyond me.

Edit: For further reading:

1 Like