Hosting Plan Resources
All ZevsHost plans run on NVMe SSD with unlimited bandwidth. But "unlimited bandwidth" does not mean "unlimited resources" — on shared hosting, dozens of other accounts run alongside yours on the same server, and the provider must make sure one heavy site cannot bring down its neighbors. This is enforced through CloudLinux LVE (Lightweight Virtual Environment): every account gets its own sandbox with hard limits on CPU, memory, and process count.
It helps to separate "disk" limits (how many gigabytes, domains, and databases you are allowed to create) from "dynamic" LVE limits (how much CPU and memory you can consume at any given moment). The first kind changes instantly when you switch plans; the second is a shared mechanism for distributing server capacity fairly among every client, and it does not depend on whether you bought Start or Business.
Plans and Resources
Disk space and the number of entities (domains, databases, mailboxes) differ between plans:
| Plan | Disk | Domains | Databases | Mailboxes |
|---|---|---|---|---|
| Start | 2 GB SSD | 3 | 5 | 5 |
| Pro | 5 GB NVMe | 10 | 20 | 20 |
| Business | 15 GB NVMe | unlimited | unlimited | unlimited |
What Counts as a Limit and What Does Not
Besides disk space and the number of domains, there are five parameters that are capped on any shared plan regardless of whether the plan description mentions them. You can see them in cPanel under Metrics → Resource Usage:
| Parameter | What it means | Typical limit |
|---|---|---|
| CPU | Share of processor time for the account | 100% of one core |
| Entry Processes | Number of concurrent PHP processes | 20 processes |
| Physical Memory | RAM used by all account processes | 1024 MB |
| I/O Usage | Disk read and write speed | 10 MB/s |
| NPROC | Total number of processes, including cron | 50 processes |
These limits are the same across every plan and come from the architecture of shared hosting itself, not from the package you picked. Each parameter is covered in detail in the article on Resource Usage in cPanel.
Real Error Messages When Limits Are Exceeded
When a site hits the Entry Processes or NPROC limit, cPanel does not show a friendly message — the process is simply killed by a signal, and the logs get an entry like this:
cpsrvd: LVE Resource limits exceeded for user: entry procs
mysqld: Too many connectionsThe visitor sees a blank page or a 500 error with no explanation. If instead a specific PHP script's memory limit is exceeded (a PHP limit, not an LVE one), error_log shows a different entry:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted
(tried to allocate 41943040 bytes) in /home/user/public_html/wp-includes/...The first case is a plan-wide limit (how many processes and how much memory the whole account gets); the second is the memory_limit directive in php.ini for a single script. Confusing the two is a common reason an administrator "raises memory_limit" and the site still crashes: the real culprit was LVE, not PHP.
When the Plan's Limits Are Not Enough
Shared hosting is built for a typical business card site, blog, or online store with average traffic. Honest signs that a plan is exhausted for objective reasons, not a misconfiguration:
- A WooCommerce store with a catalog of several thousand products and consistently high traffic hits Entry Processes even with caching enabled
- Background video processing, PDF report generation, or bulk image conversion regularly exceeds the CPU limit
- Several heavy cron jobs run at the same time and compete for the same NPROC limit
- You need your own daemon, a task queue (Redis, RabbitMQ), or a non-standard service — physically impossible on a shared plan
- You need guaranteed, not shared, CPU and disk performance
In these cases the right move is not to pick a pricier shared plan but to move to a VDS with dedicated resources and full control over the limits.
How to Check Your Limits and Current Usage
- Open cPanel and go to "Metrics" → "Resource Usage"
- Review the five graphs: CPU, Entry Processes, Physical Memory, I/O Usage, NPROC
- Look for red dots on the graphs — they mark moments when a limit was exceeded
- Match the time of the spike with entries in error_log to find the offending script
What to Do If You Run Out of Resources
- Upgrade to a higher plan in your client area if you are hitting disk, domain, or mailbox limits
- Optimize your site: compress images, enable page caching, disable unused plugins
- Check your PHP version — an outdated version runs slower and holds processes inside the Entry Processes limit longer
- Consider moving to a VDS for full control over resources if you regularly hit CPU, memory, or process limits