Every hosting plan has limits, even when the marketing says "unlimited". Understanding them helps you compare plans honestly and fix slowdowns or errors quickly.
The limits at a glance
| Limit | What it measures | When you hit it |
|---|---|---|
| Disk space | Total size of files, databases and email. | Uploads, emails and database writes fail. |
| Inodes | Number of files and folders. | No new files can be created, even with free space; see inode limits. |
| Bandwidth | Data transferred to and from visitors per month. | The site may be suspended until the month resets or you upgrade. |
| CPU | Processing power, as a share of cores. | Pages slow down while requests wait. |
| Physical memory (RAM) | Memory used by your PHP processes. | Requests fail with errors such as 500 or 503. |
| Entry processes (EP) | Simultaneous PHP requests being handled. | 508 Resource Limit Reached. |
| I/O and IOPS | Disk read/write speed and operations. | Slowdowns during heavy file or database work. |
How these limits are enforced
On MdmHost cPanel servers, CloudLinux applies CPU, RAM, entry process and I/O limits per account. That protects every account from "noisy neighbours" and keeps the server stable. You can watch your usage in cPanel → Metrics → Resource Usage; see CloudLinux resource usage in cPanel.
About "unlimited"
Unlimited disk or bandwidth always comes with fair-use rules and the CPU, RAM and inode limits above. In practice those decide how much traffic a site can handle, so compare those numbers rather than the word unlimited.
Optimise or upgrade?
- Optimise first if limits spike on simple pages: enable page caching, remove heavy plugins, block bad bots and clean up old backups and emails.
- Upgrade if you are consistently near the limits after caching, or traffic is growing steadily.