CPU
Hardware & InfrastructureCPU is the central processing unit, the primary component that executes instructions and performs calculations for a server. In web hosting, CPU capacity is typically expressed as cores, threads, or vCPU allocations, and it directly affects how quickly requests are processed. CPU limits, scheduling, and burst behavior influence performance under load, especially for dynamic sites and background tasks.
How It Works
The CPU runs the operating system and applications by executing machine instructions. Web servers (such as Nginx or Apache), application runtimes (PHP, Python, Node.js), and databases all consume CPU time to parse requests, run code, encrypt connections (TLS), compress responses, and generate pages. More available CPU resources generally means more work can be completed in parallel and with lower processing delay.
In hosting plans, CPU is often shared or allocated. On shared hosting, many accounts compete for the same physical CPU, and providers enforce limits to prevent one site from monopolizing resources. On VPS and cloud plans, you may receive a defined number of vCPUs, which represent scheduled access to underlying physical cores. Some platforms allow bursting (temporary extra CPU) while others apply strict throttling once you hit your cap, which can slow page generation and background jobs.
Why It Matters for Web Hosting
CPU availability is a key factor when comparing hosting plans because it determines how well your site handles dynamic workloads and traffic spikes. If your plan has low CPU limits, you may see slow admin dashboards, delayed cron tasks, timeouts during peak visits, or sluggish database queries even if you have enough RAM and storage. When evaluating providers, look for clear CPU allocations, transparent throttling policies, and monitoring that shows sustained CPU usage versus short bursts.
Common Use Cases
- Serving dynamic CMS pages (WordPress, Drupal) where PHP execution is CPU-bound
- Running database-heavy applications that perform frequent queries and indexing
- Handling TLS encryption, HTTP/2 or HTTP/3 processing, and response compression
- Executing background workers, queues, and scheduled tasks (cron)
- Building and deploying code, image processing, or server-side rendering tasks
CPU vs RAM
CPU and RAM solve different bottlenecks. CPU limits affect how fast requests are computed, while RAM limits affect how much data and how many processes can stay in memory without swapping to disk. A site can have plenty of RAM but still be slow if CPU is throttled, especially for uncached dynamic pages. Conversely, adding CPU will not help much if the server is running out of memory and swapping, which can make everything feel unresponsive.