ISPmanager 5 Business Documentation

CloudLinux limits

This is documentation for an outdated product. See the current documentation


CloudLinux allows restricting customers who use too much resources. You can set the limits in Cluster settings → CloudLinux limits.


LVE limits apply only to Apache processes when executing PHP or CGI scripts. Dovecot/Exim processes are not subject to limits.

LVE limits will be applied to users if individual settings are not specified. You can set individual limits when adding or editing a user. 

  • CPU load limit — in %. 100% indicates CPU speed relative to one core;
  • Total number of processes per user;
  • Physical memory — the maximum amount of physical memory that can be allocated to a user, in Mib. It includes shared memory used by the customer, as well as disk cache.
  • I/O limit — the maximum data throughput per user in Kbit/sec. It includes read and write operations; 
  • LVE concurrent connections — the maximum number of entries into LVE per user. 

CloudLinux recommendations for LVE limits

Cloud hostingHigh-end hosting
Maximum CPU100%200%
Physical memory512 MB1 GB
Total number of read/write operations1024 KB/s4096 KB/s
Number of processes within LVE2040
 Entry processes100100

MySQL Governor

You can set the limit for different periods: 1 sec, 15 sec, 1 min, 5 min, and 15 min. This allows a user to consume much system resources only during a short period of time, and forbids him doing so during a large period.  

Enable MySQL Governor and set the following limits:

  • CPU  —  in %. 100% indicates CPU speed relative to one core.
  • Read — data read in MiB/sec. Cached reads are not counted.
  • Write  — data written in MiB/sec. Cached writes are not counted.

When the customer exceeds the MySQL Governor limits, the LVE limits will be applied:

  • Maximum CPU;
  • Maximum disk I/O.