Our shared hosting packages support the following CloudLinux resource limits:
CPU speed limit, relative to a single core. Measured by % of a core, our hosting packages start from 100% (1x CPU core).
PMEM - Physical Memory limit
Physical memory limit (also includes shared memory and disk cache). Measured in MB, our hosting packages start from 1024MB.
IO throughput - combines both read & write operations. Measured in MBs per second, our hosting packages start with a limit of 8MB per second.
Restricts total number of read/write operations per second. Our packages start with a limit of 1024 operations per second.
EP - Entry processes
Limit on entry processes. Usually represents max number of concurrent connections to apache dynamic scripts as well as SSH and cron jobs running simultaneously. Our packages start with a limit of 30 entry processes.
NPROC - Number of proccess
Max number of processes within LVE, our hosting accounts start from 100 processes.
Understanding errors and faults
Sometimes your website may exhaust one of the above limits causing an error, below are some explanations of some generic error messages.
508 Resource Limit is Reached
If the CPU resources of an account are exhausted, the usage will remain at this maximum and slow down other processes running on the server. This can cause the amount of entry processes to go up as requests cannot be fulfilled as quickly- consequently the website will return a 508 Resource Limit is Reached error until existing requests are processed (subsequently further entry processes become available once requests have completed processing).
CPU faults indicate the website is not performing efficiently within the allocated resources, this is often caused by a process running on the website which tries to consume more CPU resource than are available, creating what's called a CPU Fault or CPU bottleneck.
If you are noticing CPU faults are occurring on WordPress website, you can reference our guide about troubleshooting high CPU on WordPress websites.
It also pays to observe the trend of the CPU faults, if they are irregular and occurring occasionally, it's likely the CPU faults are caused by an attack, such as a brute force attack. You could verify whether the fault is being caused by attack by viewing the websites access logs during the time the CPU fault was experienced. Configuring an application firewall would help reduce/prevent the faults caused by attacks- we recommend installing Wordfence for application security.
Generally issues with exceeding resource limits can be resolved simply by upgrading your hosting subscription to a package which offers further allocations of the resource becoming exhausted however unfortunately if you are experiencing CPU Faults or 508 Resource Limit is Reached, although upgrading your subscription would help process requests faster, you will continue to experience issues while the underlying issue within the website build is present.