This article provides guidance on CloudLinux resource limits applied to hosting. Hosting packages adhere to specific CloudLinux resource limits, including:
- SPEED: CPU speed limit relative to a single core, starting from 100% (1x CPU core).
- PMEM (Physical Memory limit): Includes physical memory, shared memory, and disk cache, starting from 1024MB.
- IO: IO throughput for both read and write operations, starting with a limit of 1MB per second.
- IOPS: Restricts the total number of read/write operations per second, starting with a limit of 1024 operations per second.
- EP (Entry processes): Limits on concurrent connections to Apache dynamic scripts, SSH, and cron jobs, starting with a limit of 30 entry processes.
- NPROC (Number of processes): Maximum number of processes within LVE, starting from 100 processes.
For detailed technical information on CloudLinux limits, refer to the CloudLinux Documentation website.
Errors and Faults:
If your website exceeds resource limits, it may result in errors. Common error messages include:
- Slow response if limited by CPU or IO, without returning an error.
- 500 or 503 errors for memory or process limits.
- A 508 Resource Limit Reached error for Entry Processes.
The most encountered faults are CPU and Entry Process faults.
CPU Faults:
Caused by internal website processes or external events. Internal causes may include poorly developed plugins or themes, inefficient page loading, or admin activity on WordPress. External causes may involve brute force attacks, bots, or successful campaigns.
Tips to troubleshoot CPU faults:
- Observe the regularity of faults.
- Identify external events by checking cPanel Resource Usage stats and access logs.
- For regular intervals, address internal website process inefficiencies.
Entry Process Faults:
If Entry Process resources are exhausted, a 508 Resource Limit Reached error occurs, preventing a single site from exhausting all Web Server processes.
In summary, exceeding resource limits at low levels is usually not a concern. Troubleshoot and identify the source of resource usage. If issues persist, consider upgrading your hosting subscription for higher resource allocations. Upgrading may help with faster request processing, but occasional resource limit faults may still occur.
