Our Web Hosting and Reseller Hosting packages come with CloudLinux-based certain level of resource usage limits, to ensure all users were only using their fair share of resources on our origin nodes.
These limits can vary depending on what hosting package is used and according to the level of resources which is recommended.
Web Hosting Resource Usage Limits
| EverCloud | EverCloud Plus | EverCloud Pro | |
|---|---|---|---|
| CPU | 1 Core | 2 Cores | 3 Cores |
| Memory | 1 GB | 2 GB | 3 GB |
| EP (Entry Processes) | 25 | 50 | 75 |
| NPROC | 100 | 200 | 300 |
| I/O Usage | 10MB/s | 10MB/s | 10MB/s |
| IOPS | 1024 | 1024 | 1024 |
| Inodes | 250000 | 350000 | 500000 |
Reseller Hosting Resource Usage Limits
| JumpStart | JumpStart Plus | JumpStart Pro | |
|---|---|---|---|
| CPU | 1 Core | 1 Core | 1 Core |
| RAM | 2 GB | 2 GB | 2 GB |
| EP (Entry Processes) | 25 | 25 | 25 |
| NPROC | 100 | 100 | 100 |
| I/O Usage | 10MB/s | 10MB/s | 10MB/s |
| IOPS | 1024 | 1024 | 1024 |
| Inodes | 250000 | 250000 | 250000 |
Understanding Limits
CPU limit allows setting CPU limit in terms of cores.
Memory limit corresponds to the amount of memory actually used by the end customer’s processes.
Entry Processes (EP) usually represent the max number of concurrent connections to Apache dynamic scripts as well as SSH and cron jobs running simultaneously.
Please note that the number of processes doesn’t represent the number of visitors you can have on your website at once.
This limit was created to prevent DoS attacks against the web server. One of the fairly popular attacks is to tie up all the Apache connections by hitting some slow page on a server. Once all Apache slots are used up, no one else will be able to connect to the web server, causing it to appear to be down. The issue is worsened by CPU limits, as once the site starts to get slow due to CPU limit – it will respond to requests slower and slower, causing more and more connections to be tied up.
To solve that, we have created entry processes (often called concurrent connections) limit. It will limit the number of concurrent connections to Apache, causing the web server to serve an error 508 page (Resource Limit Reached), once there the number of concurrent requests for the site goes above the limit.
NPROC limits purpose is to define the maximum number of processes inside LVE. Such as SSH/Cron/PHP/POP3/IMAP etc.
IO limit restricts the data throughput for the customer. They are in KB or MB/s. When the limit is reached, the processes are throttled (put to sleep). This makes sure that processes within LVE cannot go over the limit. Yet don’t stop working, nor get killed – they just work slower when the limit is reached.
IOPS limits restrict the total number of read/write operations per second. When the limit is reached the read/write operations stop until the current second expires.
Inode Limits correspond to the number of inodes on your account equals the number of files and folders you have on it. An inode usually equals one file, folder, email, or any other Unix object in a file system.
How to view your resource usage history
1) Log into your website’s cPanel
2) Scroll down to the Metrics section and click on “Resource Usage”
3) Once you are inside the Resource Usage section, the status will be displayed. To know more information, click on “Details“;
4) After clicking “Details”, choose the desired time frame you’d like to inspect and click “Submit“.
That’s all! You now know how to check on your hosting resource usage limits in your cPanel account.
Remember that you can always get in touch with our Support team throughout a ticket and ask us to do a resource usage audit for your account.
Was this helpful?
2 / 0
