Windows Server 2022/Windows 11 did away with processor grouping

[wildpig1234]

Probably just me being late to the game. But I recently found out and confirmed that win 11 /server 2022 did away with the processor grouping scheme that was used in win 10 whenever there is greater than 64 virtual threads. When this happens, window divides the threads into two groups and if your program is not specifically written to deal with processor grouping, only one processor group (meaning only after of your core/threads) is used leaving the other wasted and idling. Many programs like older versions of cpu-z and even the latest ver of userbenchmark were not written to correctly use processor grouping.

Win11/server 2022 no longer use processor grouping so that means that all programs that were written with multithreading should be able to use all the cores and threads without any worry...yeeeaa!

 

[Jorge Perez]

It still uses processor groups, the change is that programs will use all threads by default.

 

[wildpig1234]

wonder why this wasn't done in win 10. I am still using win 10 ltsc and don't want to upgrade...lol..But it seems like you have to use win11 if you have anything more than 64 threads ;(

 

[drdepasquale]

This should make a big difference in less optimized programs. I have a dual 32-Core machine, most of the time only one CPU is being utilized by a particular program.

 

[wildpig1234]

on win11, epyc 7702 shows up a one socket. There is no option to view numa node.
on win10, epyc 7702 shows up as two sockets when viewing cpu under task manager

 

[drdepasquale]

on win11, epyc 7702 shows up a one socket. There is no option to view numa node.
on win10, epyc 7702 shows up as two sockets when viewing cpu under task manager

Does Windows 10 and earlier actually treat the 65+ thread count CPUs as mutliple sockets in the form of lisensing? Or does it just appear as multiple sockets?

 

[wildpig1234]

It still uses processor groups, the change is that programs will use all threads by default.

I spoke too soon. Seems like a few less optimized programs like userbenchmark still only used half the 128 threads even under win11 ;(

Does Windows 10 and earlier actually treat the 65+ thread count CPUs as mutliple sockets in the form of lisensing? Or does it just appear as multiple sockets?

good question. i dont know enough about windows to tell you unfortunately ;( .