Shared hosting resource limits for CPU, RAM, inodes, disk I/O, and processes control different parts of a shared hosting account. Reaching one of these limits can make pages slow, stop an upload, return a 503 error, or prevent a cron job from starting. The right response depends on which resource is under pressure.
Table of Contents
What each hosting resource controls
CPU usage
CPU usage measures how much processing work your website and its services request from the server. PHP scripts, WordPress tasks, database requests, plugins, and scheduled jobs can all require CPU time.
When a site uses excessive CPU, pages can become slow. A WordPress site under high CPU and RAM pressure can also show 503 Service Unavailable errors. This relationship is described in mybox’s explanation of WordPress CPU and RAM usage.
RAM usage
RAM is the working memory used while the server runs website processes. A request may need RAM while it loads a page, runs a plugin, processes an upload, or performs another task.
High RAM use can affect site stability and speed. CPU and RAM pressure often appear together, especially when a WordPress installation performs inefficient or resource-heavy work. Slow pages and 503 errors are possible symptoms.
Inode count
An inode is a data structure in a Unix-style file system that describes a file-system object. In practical terms, your inode count is the total number of individual items stored on your disk. Files and folders therefore contribute to the count, not only the total size of the data. See Understanding the Inode Limit for the definition used by mybox.
An inode limit can affect actions that need to create another file or folder. A site may still have free disk space while reaching its inode limit because the count of stored items is a separate constraint. Failed uploads are a recognizable symptom when a new file cannot be created.
Disk I/O
Disk I/O means reading data from storage or writing data to storage. Page generation, file uploads, backups, logs, cache files, and other tasks can use disk I/O.
When disk activity is restricted, tasks that need to read or write files may take longer. Slow pages and failed uploads can therefore indicate pressure on disk I/O, although the same symptoms can also come from CPU, RAM, or inode usage.
Process limits
A process is a running task on the hosting account. A process limit controls how many account tasks can run at the same time. Website requests, background jobs, and cron jobs can all need a running process.
When the process limit is reached, a new task may not start until another task finishes. Blocked cron jobs and requests that do not complete are recognizable signs of process pressure. A process limit is different from an inode limit: processes are running tasks, while inodes are stored files and folders.
How the symptoms relate to the limit
| Resource | What it controls | Possible symptoms |
|---|---|---|
| CPU | Processing work performed by the server | Slow pages, high load, or 503 errors |
| RAM | Working memory used by running tasks | Slow pages, unstable requests, or 503 errors |
| Inodes | The number of files and folders stored on disk | Failed uploads or inability to create new items |
| Disk I/O | Reading from and writing to storage | Slow file-based tasks or failed uploads |
| Processes | The number of tasks running at the same time | Blocked cron jobs or requests that cannot start |
These symptoms can overlap. For example, a slow page does not identify one resource by itself. Check which limit is being reached before choosing an action.
When optimization is enough
Optimization is the first step when a specific task or site component causes the pressure. For a WordPress site, review the installation and the work performed by plugins, scheduled tasks, and other site functions. The goal is to reduce unnecessary CPU, RAM, file creation, disk activity, or simultaneous processes.
An inode issue needs a different approach from a CPU issue. Reducing the number of stored files and folders addresses inode pressure, while reducing expensive running work addresses CPU or RAM pressure. Removing stored items does not directly reduce the processing required by a resource-heavy request.
When a plan change is justified
A plan change is appropriate when the required resource remains above the current allowance after the relevant site work has been optimized, or when the project is growing and needs more capacity. The decision should follow the resource that is consistently under pressure rather than the symptom alone.
Traditional hosting uses predefined tiers. With Modular Web Hosting, the hosting environment can evolve with the project by adjusting individual elements, such as Add-ons or Boost Packs, instead of replacing the whole plan. The mybox plan selection explanation describes this difference.
Practical decision checklist
- Identify the symptom, such as slow pages, failed uploads, 503 errors, or blocked cron jobs.
- Match the symptom to the resource that is reaching its limit.
- Reduce the work or stored items responsible for that resource.
- Review the result after the change.
- Choose a plan adjustment when the same resource remains constrained or the project has outgrown its current allowance.
CPU, RAM, inodes, disk I/O, and processes are separate limits. Treating them as separate resources makes it easier to connect a hosting symptom to the correct action.