MdmHost runs cPanel hosting on CloudLinux, which gives every account its own fair share of CPU, memory and disk I/O. This keeps one busy site from slowing down others. The Resource Usage page in cPanel shows how close your account comes to those limits and when it was throttled.
Before you start
- Note when the site felt slow or showed errors, so you can match it to the graphs.
Open Resource Usage
- Go to cPanel → Metrics → Resource Usage (on some servers it sits in the Statistics panel or under CPU and Concurrent Connection Usage).
- The dashboard says whether your account hit limits in the last 24 hours.
- Click Details or Current Usage to see graphs, and Snapshot to see which processes and SQL queries were running at a given moment.
What each limit means
| Limit | Meaning | Symptom when hit |
|---|---|---|
| CPU (SPEED) | Share of processor time | Site becomes slow, nothing fails |
| PMEM (physical memory) | RAM used by all your processes | 500 or 503 errors, PHP killed |
| EP (entry processes) | Simultaneous PHP/CGI requests being processed | 508 Resource Limit Reached |
| NPROC | Total processes (including cron, SSH) | Errors starting scripts |
| IO / IOPS | Disk read/write speed and operations per second | Slow page loads, slow backups |
Fixing frequent limit hits
- Enable caching. On LiteSpeed servers the LiteSpeed Cache plugin for WordPress serves pages without running PHP, which removes most load.
- Block bad bots. Check Awstats or Raw Access logs for crawlers hammering the site and block them with IP Blocker or
robots.txt. - Replace heavy plugins, especially ones doing searches, statistics or related posts on every page view.
- Use real cron. Disable
WP_CRONand runwp-cron.phpevery 15 minutes with a cron job. - Optimise the database: remove old revisions, transients and log tables; add indexes for slow queries shown in Snapshot.
- Check for malware: unexpected processes or traffic can mean a compromised site.
Tip: A short burst of 508 errors during a sale or newsletter is normal. Repeated hits every day mean the site needs optimisation or a bigger plan.
When to upgrade
If the site is already cached and optimised and still reaches the limits regularly, it has outgrown its plan. Compare plans on the web hosting page, or contact support for advice.
Troubleshooting
- 508 Resource Limit Is Reached: too many requests at once (EP). Look for slow scripts or bots in the Snapshot.
- High memory with few visitors: a plugin or import job uses a lot of memory per request; check the PHP
memory_limitand the error log. - Resource Usage page missing: ask support to check the CloudLinux LVE Manager plugin for your account.