Our cPanel and WordPress hosting plans run on the CloudLinux operating system. CloudLinux isolates each hosting account into a separate LVE (Lightweight Virtual Environment) and allocates a specific resource quota per plan. This ensures that no single website can slow down the other sites on the server, and that you always have the resource quota associated with your plan at your disposal.
cPanel hosting
| Feature | cP Start | cP Basic | cP Premium | cP Pro | cP Pro 100 |
|---|---|---|---|---|---|
| vCPU | 100% | 200% | 300% | 400% | 400% |
| RAM | 1 GB | 2 GB | 3 GB | 4 GB | 4 GB |
| IO | 50 MB/s | 100 MB/s | 150 MB/s | ∞ Unlimited | ∞ Unlimited |
| IOPS | 100 | 1024 | ∞ Unlimited | ∞ Unlimited | ∞ Unlimited |
| Active connections | 20 | 40 | 80 | ∞ Unlimited | ∞ Unlimited |
You can find all the plan specifications on the cPanel hosting page.
WordPress hosting
| Feature | WP Start | WP Basic | WP Premium | WP Pro |
|---|---|---|---|---|
| vCPU | 100% | 150% | 200% | 250% |
| RAM | 2 GB | 3 GB | 3.5 GB | 4 GB |
| IO | 50 MB/s | 100 MB/s | 150 MB/s | 200 MB/s |
| IOPS | ∞ Unlimited | ∞ Unlimited | ∞ Unlimited | ∞ Unlimited |
| Active connections | 30 | 50 | 100 | 150 |
You can find all the plan specifications on the WordPress hosting page.
What do the individual values mean?
| What’s included in the plan | CloudLinux limit | Meaning |
|---|---|---|
| vCPU | SPEED | The processor time that the account’s processes can use collectively. 100% corresponds to one full processor core, whilst 200% corresponds to two. |
| RAM | PMEM | The physical memory available for simultaneous use by processes within the account (PHP, cron, SSH, Node.js and Python applications). |
| IO | IO | The read and write speeds of the hard drive. Files served from the cache are not included in these figures. |
| IOPS | IOPS | The number of disk operations that can be performed per second. |
| Active connections | EP (Entry Processes) | The number of dynamic requests served simultaneously (PHP scripts, SSH sessions, cron jobs). The serving of static files (images, CSS, JavaScript) is not included in this count. |
The number of active connections does not equate to the number of visitors. A PHP page that loads quickly takes up space for only a fraction of a second, so even 20 concurrent connections can serve significantly more visitors. The limit is typically reached due to slow scripts, traffic peaks and bots.
What happens if the site reaches its limit?
- vCPU, IO or IOPS: the site does not go down, it simply responds more slowly until the load decreases.
- Active connections: subsequent requests return a 508 error (Resource Limit Is Reached).
- RAM: CloudLinux terminates certain processes, which may result in a 500 or 503 error.
You can see how much of your quota your account is using on the cPanel Resource Usage page; see: How can I check my CloudLinux LVE resource usage in real time? The article on error counters will help you assess instances where limits have been exceeded.
If your site regularly reaches its limit and optimisation does not help, you can upgrade to a larger plan or choose a dedicated cPanel server, where all the server’s resources are yours alone.