Resource Limits: CPU, RAM, Inodes

Hosting resource limits are caps on how much of a server’s underlying capacity a single hosting account is allowed to consume. This covers CPU processing time, RAM, storage space, and inodes, which are the count of individual files and folders. They exist primarily on shared and pooled-resource hosting environments, where one server supports many accounts simultaneously and needs enforced boundaries to keep any one account from degrading performance for everyone else on it.

What Hosting Resource Limits Cover

CPU limits cap how much processing time an account can use, usually measured as a percentage of a core or a number of CPU seconds within a given window. RAM limits cap how much memory the account’s processes — PHP, database queries, background scripts — can consume simultaneously. Storage limits cap total disk space used by files and databases. Inode limits are the one most site owners have never heard of until they hit it. They cap the total number of individual files and folders on the account, regardless of their combined size. A site with hundreds of thousands of tiny cache files or email messages can hit an inode limit long before it hits its storage-space limit.

Why Resource Limits Matter

On a shared server, resource limits are what prevent one account from starving every other account on the same machine of CPU or RAM. They’re a fairness mechanism as much as a restriction. But hitting a limit has real, immediate consequences for the account that hits it: throttled performance, temporary process termination, or in some cases account suspension until usage drops or the plan is upgraded. Understanding which limit applies, and which one is closest to being reached, is essential to diagnosing unexplained slowdowns or sudden errors on a shared or budget plan.

How to Evaluate Hosting Resource Limits on a Plan

Ask for the specific numbers, not just marketing language like “generous resources.” That means CPU allocation, often stated in cores or CPU-seconds, RAM allocation in MB or GB, storage in GB, and inode count specifically. Check whether the control panel exposes real-time usage against each limit, since a plan that hides this information makes it much harder to diagnose a resource-related slowdown before it becomes an outage. Also confirm what happens at the limit — throttling, temporary suspension, or an upgrade prompt — since the practical impact differs significantly between these outcomes.

CPU, RAM, and Inode Limit Benchmarks

Resource	Typical shared hosting limit
CPU	Equivalent of 1–4 cores’ worth of processing time, often burst-limited
RAM	512MB–2GB per account
Inodes	100,000–300,000 files/folders
Storage	10–100GB depending on plan tier

A WordPress site with a large media library and aggressive page-cache plugin can accumulate well over 100,000 cached files. This makes inode limits a genuinely common issue on budget shared plans, distinct from and often reached before any storage-space concern.

How Hosting Types Differ on Resource Limits

Shared hosting enforces the tightest and most numerous resource limits, since it’s structurally built around many accounts sharing one physical server’s finite capacity. This is the direct trade-off for its low price. VPS hosting allocates dedicated, guaranteed CPU and RAM to each account rather than pooling it, which removes the “noisy neighbor” version of resource contention, though the plan still has a fixed ceiling based on the virtual machine’s specs. Dedicated hosting removes shared-resource limits entirely, since the customer has the entire physical machine’s capacity available, though the machine itself is still a fixed, finite resource. Cloud hosting can effectively remove hard resource limits altogether on autoscaling configurations, since additional capacity can be provisioned automatically as demand grows. See hosting scalability for how that mechanism works.

How Resource Limits Affect Speed, Security, and Cost

Speed is the most direct connection. Hitting a CPU or RAM limit is one of the most common causes of the intermittent slowdowns covered in why is my website slow, and it’s frequently misdiagnosed as a code problem when it’s actually a plan-tier ceiling being reached. Security intersects less directly, though a compromised account running malicious scripts, a cryptomining script for example, often shows up first as an unexplained resource-limit breach. This makes resource monitoring an early-warning signal for certain kinds of compromise. On cost, resource limits are the mechanism that keeps entry-tier shared hosting cheap. The provider can offer a low price precisely because usage is capped tightly, and upgrading past a resource ceiling is one of the most common reasons a site moves from shared hosting to VPS hosting. See hosting terms of service, explained for how these limits are typically documented contractually.

Hosting Resource Limits FAQ

What’s the difference between running out of storage and running out of inodes?

Storage is about the total size of files in gigabytes. Inodes are about the total count of individual files and folders, regardless of size. A site can run out of inodes while still having plenty of storage space free, especially with many small cache or email files.

How do I know if I’m hitting a resource limit?

Symptoms include intermittent 503 errors, sudden slowdowns without a clear code-level cause, or an explicit resource-usage warning from the host. Most control panels show real-time usage against each limit if you know where to check.

Do VPS and dedicated plans have resource limits too?

Yes, but they’re set by the plan’s specs, or the physical hardware, rather than by pooled fair-use enforcement across other tenants. This is why they generally feel less restrictive than an equivalent shared plan.

For a related error pattern, see 503 service unavailable; for the full attribute set, see web hosting features.