What Are vCPU Cores?

A vCPU (virtual CPU core) is a slice of physical CPU capacity assigned to your VPS by the hypervisor. Your plan’s vCPU count tells you how much parallel processing power the VM can use — not a dedicated physical core, but guaranteed virtual capacity on the host.

Overview

CPU is one of the three main VPS resources (with RAM and disk). vCPU specs appear on every VPSGrid plan page. Understanding vCPUs helps you size workloads and interpret “slow server” complaints. Start with What Is a VPS? if you are new to virtual servers.

Physical CPU vs vCPU

When Ubuntu reports “2 CPUs,” that usually means 2 vCPUs — not that you own two entire physical cores exclusively 24/7. The hypervisor maps your vCPUs to host hardware fairly alongside other VMs.

How vCPUs affect performance

• More vCPUs — better for parallel work (multiple PHP-FPM workers, database threads, build farms, game servers with many entities)
• Fewer vCPUs — fine for small sites, cron jobs, VPNs, and low-traffic APIs
• CPU-bound vs I/O-bound — video encoding and compiles are CPU-bound; a busy WordPress site may be RAM or disk bound instead — check all three resources

Adding vCPUs without enough RAM can cause swapping and make performance worse. Pair with How RAM Works on a VPS and What Is NVMe Storage?.

CPU steal and noisy neighbors

Steal time (often shown as %st in Linux top) indicates your VM wanted CPU cycles but the hypervisor gave them to other guests first. Occasional steal is normal on shared hosts. Sustained high steal under your normal load may mean:

• The host is oversubscribed or under heavy load
• Your workload needs a larger plan or a different tier
• Another VM on the host is spiking (provider-side issue — worth a support ticket if persistent)

On Linux, run top and watch the st column. On Windows, use Task Manager and Performance Monitor for sustained high CPU outside your apps.

Choosing the right vCPU count

Rough starting points (adjust for your app):

Confirm current vCPU counts on the live store — Spark / Flame / Blaze tiers scale CPU with the plan:

• Linux VPS store
• Windows VPS store

Monitoring CPU inside your VPS

VPSGrid is unmanaged — you diagnose inside the guest OS:

1. Linux — top, htop, mpstat, application-specific profilers
2. Windows — Task Manager → Performance, Resource Monitor, Performance Monitor
3. Web stacks — PHP-FPM pool sizes, worker counts, and database slow query logs often explain CPU spikes better than raw graphs alone

If CPU is low but the site feels slow, investigate RAM, disk I/O, or network — Why Is My VPS Slow?.

Common misconceptions

• “1 vCPU = 1 full physical core always.” It is virtual capacity; scheduling is shared on the host.
• “More vCPUs always means faster website.” Single-threaded bottlenecks (one heavy PHP request) may not use extra cores.
• “High CPU is always the provider’s fault.” Runaway cron jobs, crypto miners, or misconfigured loops are common customer-side causes — Security Responsibilities on Unmanaged VPS.

Frequently Asked Questions

Related Articles

• How RAM Works on a VPS
• What Is NVMe Storage?
• What Is KVM Virtualization?
• Why Is My VPS Slow?
• VPS vs Shared Hosting

Need More Help?

Questions about plan CPU specs or persistent performance issues: open a ticket at billing.vpsgrid.net with your service ID and top/Task Manager output.