Web Hosting Resource Limits: CPU, RAM, IO and Entry Processes
Your site was running fine for months, then one afternoon it started throwing errors under load and nobody could tell you why. The answer is usually sitting in a resource limit you never knew existed, quietly capping something long before your storage bar looked full.
Storage is the number everyone checks first, and it’s often the least important one. CPU, RAM, IO and entry processes are what actually decide whether your site holds up when several visitors land on it at once.
This article walks through what each of those terms means, why they matter more than storage in practice, and what GoodHost’s own WordPress plans publish for each of them. It’s part of the broader Web Hosting Explained hub if you want more background first.
Short answer: CPU, RAM, IO and entry process limits control how much processing power, memory, disk speed and simultaneous activity your hosting account is allowed at any moment. Hit one of them and your site slows down or throws errors, even if you have plenty of storage left. GoodHost’s WordPress plans publish exact figures for all of them, which most hosts don’t do.
What do CPU, RAM, IO and entry processes actually mean for a website?
CPU is processing power, measured as a percentage of a core your account can use. RAM is working memory for running code. IO is how fast your account can read and write to disk, and entry processes are the number of scripts, like PHP requests, that can run for your account at the same instant.
Every page load, plugin action or background task on your site uses some combination of all four. A busy WooCommerce checkout, a backup running in the background, or a spike of visitors arriving at once can all push one of these limits before the others.
Why do these limits matter more than storage space?
Storage only becomes a problem when it fills up, which happens slowly and predictably. CPU, RAM, IO and entry process limits get hit suddenly, often during exactly the moment your site is getting real traffic, and the result is a slow or broken page rather than a tidy warning email.
A site can sit at 10% of its storage allowance and still fall over under load if its CPU or entry process limit is too low for what the site is actually doing.
What happens when a website hits its resource limit?
Pages load slowly, time out, or return server errors until usage drops back under the limit. On some hosts this affects your account only, on others sharing a badly managed server can drag other accounts down too, which is part of why isolated, published limits matter.
- Pages that time out or load noticeably slower during busy periods
- Intermittent 500 or 503 errors that seem to come and go
- Background tasks, like backups or scheduled plugins, failing to complete
- Checkout or form submissions stalling under moderate traffic
How do GoodHost’s WordPress plans allocate these resources?
GoodHost’s WordPress hosting runs on Enhance containers rather than CloudLinux, with one site per plan and no visit caps. Each tier publishes its actual CPU, RAM, entry process, IO and IOPS allocation rather than hiding behind a vague “visits per month” figure.
| Plan | Price/month + GST | Storage | vCPU | RAM | Entry processes | IO | IOPS |
|---|---|---|---|---|---|---|---|
| WP 10 | $45 | 10 GB | 400% | 4 GB | 40 | 8 MB/s | 4,000 |
| WP 20 | $79 | 20 GB | 600% | 6 GB | 60 | 12 MB/s | 6,000 |
| WP 50 | $169 | 50 GB | 800% | 8 GB | 100 | 16 MB/s | 8,000 |
You can see the full lineup, including the cPanel plans, on the GoodHost hosting page. If you want to understand cPanel itself before comparing the two product lines, our guide to what cPanel is covers the basics.
Why do most hosts sell “visits per month” instead of actual resource limits?
Visits per month is a rough proxy for load, not a resource guarantee, and it’s easier to market than a technical spec sheet. Two sites with the same monthly visits can place very different demands on CPU and entry processes depending on what the site actually does on each page.
A heavy WooCommerce store with 5,000 visits a month can strain a server harder than a static brochure site with 20,000. Publishing the actual CPU, RAM, IO and entry process numbers, as GoodHost does for its WordPress plans, gives you something you can actually check against what your site needs, rather than a marketing figure to take on faith.
How do you know which plan you need?
Match the plan to what your site does, not just its traffic volume. A simple brochure site with light traffic rarely stresses even the smallest tier, while an active WooCommerce store, a membership site or anything running frequent background tasks benefits from higher entry process and IO allowances regardless of visitor count.
If you’re still deciding between hosting types altogether, our guide to shared vs VPS vs dedicated hosting is worth reading alongside this one, since resource limits work differently across each.
Frequently asked questions
What is an entry process in web hosting?
An entry process is a script, most commonly a PHP request, that’s actively running for your account at a given moment. Each page load, plugin action or background job can use one or more entry processes at once, and hitting the limit causes new requests to queue or fail until others finish.
What does vCPU percentage mean on a hosting plan?
It’s the share of a processor core your account is allowed to use, expressed as a percentage. 400% roughly means the equivalent of four full CPU cores’ worth of processing power available to that account, spread across whatever tasks are running at the time.
Can I upgrade my plan if I keep hitting resource limits?
Yes, moving to a higher tier with more CPU, RAM, IO and entry processes is the standard fix once you’ve confirmed that’s actually what’s being hit. GoodHost bills upgrades pro rata, so you’re only charged the difference for the remainder of the billing cycle.
Does more storage fix slow website performance?
Rarely on its own. Storage affects how much you can save, not how fast your site processes requests. If pages are slow or timing out under load, CPU, RAM, IO or entry process limits are the more likely cause, not the amount of free disk space remaining.
Why does my site slow down even though I’m not near my storage limit?
Because storage and performance are governed by separate limits. A site can have plenty of spare storage and still hit its CPU, RAM, IO or entry process ceiling during a busy period, which shows up as slow pages or errors rather than a storage warning.
If you want to check whether your current plan actually matches what your site needs, the resource figures for each GoodHost WordPress tier are listed in full on the hosting page, so you can compare them against what your site is doing before you upgrade anything.