How do I verify a dedicated server’s CPU sockets, cores and threads?
CPU sockets, physical cores and logical processors describe different aspects of a server. Simultaneous multithreading can expose more logical processors than physical cores, but it does not make each thread equivalent to an additional physical core. Compare the operating-system view with the ordered server model and firmware settings.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Read the processor topology
Run this on the bare-metal operating system rather than inside a virtual machine if the aim is to verify the physical machine.
lscpuReview Socket(s), Core(s) per socket, Thread(s) per core, online CPUs and the reported model. The exact fields vary by architecture.
2. Check online CPU placement
Inspect per-CPU topology to identify offline processors or an unexpected placement. Firmware inventory provides an additional source, but firmware-reported values can be incomplete.
lscpu -e=CPU,ONLINE,SOCKET,CORE,NODERows describe logical CPUs, not separate physical processor packages. Confirm any mismatch with the provider’s hardware inventory and supported BIOS configuration.
Check the result
- The expected physical configuration, enabled cores and online logical CPU count reconcile with the server specification. Workload limits and software licensing may use different counting rules.
Troubleshooting
- The count is lower than ordered
- Check whether this is a guest, whether CPUs are offline and whether firmware intentionally disables cores or SMT before assuming hardware is missing.
- The model name looks correct but performance differs
- Clock policy, thermals, memory locality and workload parallelism can affect performance independently of the model label.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.