A vCore (virtual core) is a virtualized CPU core allocated to your server in VPS or cloud hosting environments, representing a portion of the physical processor's capacity.

Instead of having exclusive access to an entire physical CPU core, your server receives time slots and processing power from the host machine's CPU cores, which are shared among multiple virtual machines using sophisticated scheduling algorithms. Understanding vCores is essential for choosing the right hosting plan and predicting server performance.

What Is a vCore?

A vCore is a virtualized representation of a physical CPU core that your virtual machine (VM) sees as its own processor. The hypervisor (virtualization software like VMware, KVM, or Proxmox) divides physical CPU resources into time slices and allocates them to virtual machines based on their assigned vCores.

How vCores Work

When you have a server with 4 vCores:

Your VM's operating system sees 4 separate CPU cores
The hypervisor schedules your VM's workload across the physical host's CPU cores
Each vCore receives processing time from one or more physical CPU threads
Multiple VMs share the same physical cores through time-slicing

For example, if a physical server has 16 physical cores and runs 8 VMs with 4 vCores each, the hypervisor schedules 32 total vCores across 16 physical cores, meaning each physical core handles approximately 2 vCores worth of workload.

vCore vs Physical Core

Aspect	Physical Core	vCore
Dedicated Access	Exclusive access to the core	Shared time slots on physical cores
Performance	Consistent, predicable	Depends on the host load and other VMs
Resource Isolation	Complete isolation	Virtual isolation, potential contention
Cost	More expensive	More cost-effective
Best For	High-performance, consistent workloads	Variable workloads, shared hosting

💡

Key difference: A physical core is yours alone, while a vCore shares time with other VMs competing for the same physical resources.

Shared vs Dedicated vCores

Shared vCores

Shared vCores (also called "burstable" or "shared CPU") mean your VM competes with other VMs for CPU time:

Pros: Very cost-effective, can handle bursty workloads
Cons: Performance varies based on neighbor activity, not suitable for consistent high-load applications
Best for: Websites with light traffic, development servers, applications with variable CPU needs

On shared vCores, your Minecraft server might run smoothly at 20 TPS when neighbors are idle, but drop to 15 TPS when other VMs on the same host become active.

Dedicated vCores

Dedicated vCores (or dedicated CPUs) guarantee your VM has exclusive access to physical CPU resources:

Pros: Consistent performance, no resource contention, predictable behavior
Cons: More expensive than shared vCores
Best for: Game servers, production applications, high-traffic websites

With dedicated vCores, your Minecraft server maintains stable 20 TPS regardless of what other VMs are doing.

vCore Performance Factors

CPU Overcommitment

Hosts can allocate more vCores than physical cores exist called overcommitment or oversubscription:

Example: A 16-core server running 32 vCores (2:1 ratio)
Impact: When all VMs are active, each vCore receives less than a full core's worth of processing power
Risk: Heavy overcommitment (4:1 or higher) causes performance bottlenecks

Quality hosting providers limit overcommitment ratios to maintain performance. Budget providers often overcommit aggressively, resulting in poor game server performance.

Resource Contention

When multiple VMs with many vCores compete for the same physical CPU, resource contention occurs:

VMs must wait for CPU time slots to become available
Context switching overhead reduces efficiency
Performance becomes unpredictable and inconsistent

This is why dedicated vCores perform better. No waiting for CPU access.

Physical CPU Clock Speed

A vCore's performance depends on the underlying physical CPU:

1 vCore on an Intel Xeon E5-2680 v4 (2.4 GHz) ≠ 1 vCore on AMD EPYC 7763 (3.5+ GHz boost)
Higher clock speeds mean better single-threaded performance
Important for Minecraft, which relies heavily on single-core speed

Always check what physical CPU your vCores run on, not all vCores are equal.

Hypervisor Scheduling

Different hypervisors have different scheduling algorithms:

VMware ESXi: Sophisticated CPU scheduler with proportional share allocation
KVM/Proxmox: CPU pinning for dedicated vCore assignment
Hyper-V: Dynamic CPU scheduling with power management

Better hypervisors minimize overhead and improve vCore efficiency.

vCores for Minecraft Servers

Minecraft servers benefit most from:

High clock speed vCores: Single-threaded performance is critical
Dedicated vCores: Consistent TPS requires predictable CPU access
Low overcommitment ratios: Avoid hosts that oversell resources

How Many vCores Do You Need?

Server Type	Recommended vCores	Notes
Vanilla (1-10 players)	1-2 vCores	Single-threaded, needs high clock speed
Vanilla (10-50 players)	2-4 vCores	Background tasks use extra cores
Modded (10-30 players)	4-6 vCores	Mods increase CPU demand
Modded (50+ players)	6-8+ vCores	Heavy modpacks need multiple cores
Proxy Networks	1-2 vCores per proxy	Proxies are lightweight

💡

Note: Clock speed matters more than vCore count for Minecraft. 2 vCores at 4.0 GHz often outperform 4 vCores at 2.4 GHz.

Monitoring vCore Usage

Check if your server needs more vCores:

High CPU usage indicators:

/spark profiler shows >80% CPU usage during normal gameplay
TPS consistently below 20
Player report lag during peak hours
High "time spent ticking" in timings reports

Normal CPU usage:

CPU usage fluctuates between 30-70%
TPS stays at 20 consistently
Occasional spikes during intensive operations (chunk generation, autosave)

If CPU stays maxed at 100%, you need more vCores or a higher clock speed CPU.

Common Misconceptions

"More vCores Always Mean Better Performance"

False. Minecraft's main thread is single-threaded, giving it 8 vCores instead of 4 won't improve TPS if the server only uses one core for ticking. Focus on clock speed and dedicated access instead.

"1 vCore = 1 Physical Core"

False. A vCore is a time-shared portion of one or more physical cores, not a 1:1 mapping. Its actual performance depends on host load, overcommitment, and scheduling.

"Shared vCores Are Always Bad"

False. For low-traffic or development servers, shared vCores work fine and save money. But for production game servers with consistent player counts, dedicated vCores are essential.