LVE is a kernel-level technology developed by CloudLinux that isolates each tenant on a server into their own environment, preventing one tenant from impacting others.
More About LVEs
Resource Allocation: Controls and limits resources like CPU, RAM, and I/O for each tenant.
Security and Stability: Enhances the security and stability of shared hosting servers.
Monitoring and Management: Allows hosting providers to monitor and manage resource usage efficiently.
Application: Particularly useful in shared hosting environments to ensure fair usage and prevent abuse.
Understanding LVE 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 represents 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.
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 getting 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 corresponds 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.