CloudLinux Limits

The server resources assigned per Shared Hosting Plan are limited by CloudLinux in the following way:

Entry-Level Plan:
CPU: 1 CPU core
Pysical Memory: 512 MB
Entry Processes/EP: 20
I/O: 1Mbps

Standard Plan:
CPU: 1 CPU core
Pysical Memory: 1024 MB
Entry Processes/EP: 20
I/O: 1Mbps

E-commerce Plan:
CPU: 1 CPU core
Pysical Memory: 1536 MB
Entry Processes/EP: 25
I/O: 1Mbps

Business Plan:
CPU: 1 CPU core
Pysical Memory: 2048 MB
Entry Processes/EP: 25
I/O: 1Mbps

Glosary

CPU Usage - specifies how much of the allocated CPU resources you are currently using. The amount of CPU resources we provide to each account is the percentage of the server’s resources.

If your account hits this limit, your website will slow down.


Physical Memory Usage/pMEM/pM
(RAM) is the actual memory allocated for your account. Virtual memory is usually a file on a disk drive that the operating system uses to store information (swap-to-from) when the real memory becomes full, for instance the page (swap) file on a Linux system. Therefore, if you try to publish a big post, it might take all physical memory to do so, but after some time it will be normalized.

If your account hits this limit, your website will show a 500 error message.


Entry Processes/EP
- the number of processes that enter your account. For example, every PHP page that is accessed by a user will usually generate a single entry process. Many people misinterpret this value as “number of visitors you can have on your website at once”. Whilst it is true that each visitor accessing a PHP page will spawn an entry process, these processes usually end so quickly that it is extremely unlikely that 10 will be spawned concurrently and at a single moment unless you had a significantly large number of simultaneous visitors on your website at once. SSH sessions and cron jobs also count as entry processes.

If your account hits this limit, your website will show a 508 error message.


Number of Processes/nPROC/nP
- this limit is similar to the above but includes all processes generated by the account rather than the specific PHP, SSH or cron jobs. This number is typically very low, even under high activity, as non-PHP tasks execute and complete even more quickly.


I/O Usage
(input/output) represents how much I/O (or disk activity) your account is using. Any task which makes use of the servers disk drive (such as reading or writing to the server) will consume I/O.

If your account hits this limit, your website will slow down.

Acronyms

CPU - CPU limits
vMEM/vM - Virtual Memory limits
pMEM/pM - Physical Memory limits
EP - Entry Processes
nPROC/nP - Number of Processes
IO - Input/Output limits

a - average used
l - limit set for account
m - maximal used
f - failure

Help, I am hitting a limit! How can I reduce my resource usage?


You can try disabling plugins, disabling any special features, and/or repairing your database(s).

You can look into optimizing your script(s). Your webmaster or the script developers should be able to assist with this.

Still need more resources?


If you're unable to reduce your account's resource usages, it is simply no longer suitable for a shared hosting environment. You might want to consider upgrading to one of our virtual servers if this is the case. You can view our virtual server offerings at our VPS Hosting page.

  • 5 Users Found This Useful
Was this answer helpful?