On this page
Setting LVE resource limits with CloudLinux Manager
CloudLinux LVE Manager lets you set per-user resource limits in WHM to keep your server stable and prevent any single account from hogging resources.
If you're running CloudLinux OS on your Kualo server, you can access the CloudLinux LVE Manager via WHM to set resource limits for each of your users, ensuring optimal system stability and performance.
For Fully Managed customers, we've already set an overall limit on your WHM account so you don't exceed the total resources available on the server - leaving sufficient headroom for the core operating system to function smoothly. This article explains how to set individual resource limits for each of your users, and why doing so matters for a stable, high-performing server.
Why set resource limits?
Resource limits prevent any single user from monopolising the server's resources, ensuring a smooth and stable experience for everyone. This is particularly important when you're hosting multiple websites or applications on the same server.
While imposing limits might initially seem restrictive, it's a crucial step for maintaining server stability. Without these safeguards, the actions of a few accounts can destabilise the server and affect all your clients. If an account is regularly hitting its limits, that's a signal it may need more resources or further optimisation. If the site is already fully optimised, upgrading to a higher-tier package is straightforward - just get in touch.
Types of limits and their impact
| Limit type | Description | Recommended? | Impact of hitting the limit |
|---|---|---|---|
| CPU | Percentage of CPU available to the LVE. 100% equals one CPU core. | Yes - minimum 100% | Website may become slow or unresponsive. |
| Memory | Amount of RAM in MB. | Yes - minimum 512 MB | Out-of-memory errors, website crashes. |
| Number of processes (nPROC) | Total processes that can run in the LVE. | Yes - minimum 60 | Unable to spawn new processes, affecting website functionality. |
| Entry processes (EP) | Number of entry processes (e.g. Apache/HTTPD processes). | Yes - set to roughly 1/3 of your nPROC value | Users may see 508 errors when visiting the website. |
| IO | IO speed in KB/s. | Optional | Slow file read/write operations, affecting load times. |
| IOPS | Input/output operations per second. | Optional | Slow database queries and file operations. |
Methodologies for setting limits
We recommend setting limits based on WHM packages. This gives you a clear, manageable way to understand and control the resources allocated to each user, and makes upgrading or downgrading resources straightforward. You can also set limits on a per-user basis on the fly, though this becomes burdensome when managing many accounts. Default limits act as a safety net for clients on custom packages that don't have pre-defined limits.
Using WHM packages
- Log in to WHM and navigate to the CloudLinux LVE Manager.
- Go to the Packages tab.
- Choose the package you want to modify and set the desired limits for CPU, IO, IOPS, Memory, nPROC, and EP.
- Save your changes.
On-the-fly limits for individual users
- Log in to WHM and navigate to the CloudLinux LVE Manager.
- Go to the Users tab.
- Choose the user you want to modify and set the desired limits.
- Save your changes.
Setting default limits
- Log in to WHM and navigate to the CloudLinux LVE Manager.
- Go to the Options tab.
- Set the limits you want to apply as the default.
- Save your changes.
Assessing usage in cPanel
Users can check their own resource consumption via the Resource Usage tool in cPanel.
- Log in to cPanel.
- Go to the Metrics section and click Resource Usage.
- Review the usage data to make informed decisions about setting or adjusting limits.
Suggested resource limits
The right limits depend on several factors:
- The specification of your server - more RAM and CPU cores means more resources to share out.
- The number of sites you host - fewer sites means each one can be given more headroom.
- The requirements of each site - each website should have enough resources to meet its operational needs.
The table below gives typical starting points, assuming you're hosting several sites and want packages suitable for small, mid-range, and large customers.
| Type of site | CPU (%) | IO (KB/s) | IOPS | Memory | nPROC | EP |
|---|---|---|---|---|---|---|
| Small / brochure sites | 100-200% | Not limited | Not limited | 512 MB - 1 GB | 60 | 20 |
| Mid-range / e-commerce | 200-300% | Not limited | Not limited | 2 GB - 3 GB | 150 | 50 |
| Higher-range e-commerce | 300-500% | Not limited | Not limited | 4 GB - 8 GB | 300 | 100 |
These are guidelines only. We strongly recommend consulting with us to tailor these limits to your specific server resources and workload.
Effective resource management is key to a stable, high-performing server. If you'd like advice on the right limits for your setup, don't hesitate to get in touch - we're happy to help.