Does one VPS vCPU mean one dedicated physical core?
A vCPU is a processor presented to the guest by the virtualisation platform. Its relationship to physical cores depends on scheduling, topology and the service allocation policy. A displayed vCPU count alone does not prove exclusive access to physical cores.
Instructions
1. Read the allocation terms
Check the number of vCPUs, whether CPU time is shared or reserved, any fair-use limits and the workload’s licensing requirements. Ask for clarification if the service description uses dedicated CPU without defining its scope.
2. Inspect the guest view
On Linux, read the topology presented to the operating system.
lscpuThe listed CPUs, sockets and cores describe the topology exposed to the guest. They do not independently reveal the provider’s complete physical host or scheduling policy.
3. Measure the actual workload
Assess sustained response time, throughput and resource pressure under an authorised representative workload. CPU clock labels and vCPU counts cannot predict every application’s performance, particularly when storage or network latency is the limiting factor.
Check the result
- The guest-visible processor count matches the purchased allocation.
- The CPU-sharing or reservation terms are understood before using them for capacity or licensing decisions.
Troubleshooting
- The guest reports unexpected socket or core counts
- Virtual topology can be configured independently of physical topology; compare the allocation and platform documentation.
- More vCPUs do not improve the application
- Check whether the workload is single-threaded, blocked on I/O or constrained elsewhere.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.