How to find number of cores in windows server 2003




















I don't know that all three expose the information in the same way, but if you can safely assume that the NT kernel will report device information according to the POSIX standard which NT supposedly has support for , then you could work off that standard. However, differing of device management is often cited as one of the stumbling blocks to cross platform development.

I would at best implement this as three strands of logic, I wouldn't try to write one piece of code to handle all platforms evenly. Is that what you're trying to find? The difference is that GetLogicalProcessorInformation doesn't support setups with more than 64 logical cores, which might be important for server setups, but you can always fall back to GetLogicalProcessorInformation if you're on XP.

You may use the library libcpuid Also on GitHub - libcpuid. As can be seen in its documentation page :. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 11 years, 7 months ago. Active 2 years, 2 months ago. Viewed 49k times. Improve this question. Royi 4, 6 6 gold badges 41 41 silver badges 57 57 bronze badges.

Check this out - stackoverflow. Didn't you just ask the same question a couple days ago? Have you abandoned this question? Did you ever get this resolved successfully? Do you still need help with this? Add a comment. Active Oldest Votes. Improve this answer. Would you care to elaborate? Alex, The Xeon E in the example above was from a machine with two processor packages so the numbers are correct.

However, the i7 does cause problems with this code. There weren't many i7s when I posted that solution. It seemed to worked at the time. With the introduction of the i7 Intel made their own CPID instruction almost impossible to use for this purpose. The code is still not working. It reported 16 logical cores on a iU cpu. The code did work at one point, but it's incorrect even for a made i3 5x0 processor because around that time Intel decide to add gaps in the APIC id space.

See my answer in another thread for details. Show 10 more comments. This is a very simple solution but it does not differentiate hardware threads, a. Yes you are right I missed this detail, so should I delete my post? Don't delete your post, this information is very helpful. Thank you it helped me! Ivanov 1, 11 11 silver badges 22 22 bronze badges. I've upvoted this because it works. For the textual record and in case the link goes dead at some point , the msdn link in this answer uses GetLogicalProcessorInformation, which works ok on most recent versions of Windows.

Z boson Z boson Well, I upvoted you because this is better than the other answers, but you are not technically answering the question. You can then use PowerShell to parse the text report, for example by doing something along these lines:. Jaap - same ansswer as using WMI. You ned to get model and convert. The other issue with WS and earlier is that the information is on a line with no lable so 'Processor" gets nothing usefule. WMI gives us teh model and stepping and the number of physical processors on record per physical processor.

It seem to me to be the easies and most direct way to do this. THis also avoids counting hyperthreadded instances. This will be a hectic task for 20 computers. So looking into the vendor site to figure out the cores of that model will be enough to get accurate answer? Multi-core processors did not get marketed until WS Almost no one sold cores. They all sold multi-processor systems which do not need anything special just count the processors returned via WMI.

I see there are 2 cores? Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. So, I'm feeling confused. You say that "Windows is the same idea"; but it appears from what I'm reading that only 4 cores are accessed in Standard Edition, whereas 32 cores 4 sockets are supported in the version. Just so I understand; if I have a dual quad-core system with Standard, 4 cores would always stand idle?

I don't know why it wouldn't be. I haven't checked yet because it's not installed yet. So, it sounds like we can interpret Microsoft's reference as sockets, not cores. Does everyone agree this validates my conclusion? Scott Hanson 4 Tellurium. So Standard edition is up to 4 sockets Enterprise is up to 8 sockets, and Datacenter can go as high as 64 or with a different SKU. Thanks, that's the information I was looking for. Post Reply.



0コメント

  • 1000 / 1000