5 ms·
Afaik, Windows "Home" is limited to 1, "Professional" to 2 and "Pro for Workstations" to 4 CPUs. Can be nicely tested with virtualization (e.g. KVM). Just assi
by thg 5y ago
Afaik, Windows "Home" is limited to 1, "Professional" to 2 and "Pro for Workstations" to 4 CPUs.
Can be nicely tested with virtualization (e.g. KVM). Just assign multiple CPUs with one core each and Windows will only use the amount of "CPUs" that the license allows. A single CPU with a bazillion cores is no problem, though.
I only know this because I ran into that exact pitfall several times already.
- dm319 5y agoYes wasn't this an issue when the early benchmarks of the threadrippers came out? I think there was some kind of thread limit.
- thg 5y agoApparently there was, and probably still is (process groups): https://www.anandtech.com/show/15483/amd-threadripper-3990x-review/3 https://www.anandtech.com/show/15483/amd-threadripper-3990x-... And here's a table about hardware restrictions for Windows 10: https://en.wikipedia.org/wiki/Windows_10_editions#Comparison_chart https://en.wikipedia.org/wiki/Windows_10_editions#Comparison... Looks like Windows 10 Pro is limited to 128 cores / threads per CPU. Guess I was a bit off with my "bazillion" remark above, but who with access to that kind of hardware would ever want to waste it on Windows anyway?
- dm319 5y agoSeems so arbitrary and petty. But thankfully I like another OS that doesn't do this! :)
- Dylan16807 5y agoThe process group thing isn't pettiness, it's an implementation flaw.