What is LVE and what is it used for?

LVE is a kernel-level technology developed by the CloudLinux team which operates in a way similar to container virtualization. The LVE Manager enables you to maintain precise control over your server’s resources, including CPU, IO, inodes, the number of processes and connections that each individual cPanel account can use. Thanks to CloudLinux, you can ensure for your customers the resources they leased without depriving other users from their resources. LVE enables many crucial settings:

• CPU limitation
  Limits CPU usage for each individual user. When a user reaches the set CPU limits, their processes are decelerated in order to prevent the misuse of server resources. Processor limitations are crucial in preventing individual users from slowing down or even blocking the entire server and making it unresponsive.
• Memory limitation
  Limits memory usage per user. Memory limitations are important in preventing the overuse of server memory which can lead to server congestion. Memory limitations are also fundamental in protecting the server from destroying important caches that can help increase the speed and reduce the load of the server.
• I/O limits
  Offers the limitation of data throughput per user. The bandwidth is measured in kB/s, and, upon reaching the limit, the processes are reduced. Since IO is one of the weakest shared hosting resources, setting a ceiling for user usage is vital because it enables stable work for all users, instead of several users with extremely complex sites congesting the disks.
• Process number limitation
  Limits the number of simultaneous processes within the LVE for each user. After the limit has been reached, no new processes can be created until one of the existing processes is complete. This effectively prevents fork bombs and similar DOS attacks.
• Entry process limitation
  Limits the number of entry processes within the LVE for each user. A single entry process actually represents a single website visitor. This limitation is important in order to prevent a single website from taking up all Apache resources and making the server unresponsive due to overload.
• MySQL limits
  MySQL Governor enables you to set a resource limitation per user. You can set a limitation for CPU and IO reading and writing, thus preventing individual users from taking up the majority of MySQL server resources. Nowadays, MySQL data launches most web applications and it’s important to monitor those applications.
• Inode limits
  Inode is a type of data structure that describes file system objects – files and directories. Only a limited number of inodes is in each file system, and, after those are used, no new files can be created. Limitations are enforced through file system quotas per user.