LVE stands for Light Weight Environment, it is CloudLinux Virtual Environment limited by CPU, RAM, I/O, UID and GID. Standard CloudLinux LVE feature is used in POA Linux Shared Hosting NG module.
Dynamic website content is executed through cgid - standalone cgid processes which retrieve site configuration and create LVE to execute dynamic site content.
LVE is unique for a website and is being created on demand when request to the site is received. All dynamic requests to one website come to the same LVE and share CPU and RAM limits. LVE is removed by kernel once all site's processes are finished. Website CPU, RAM, I/O, UID, GID limits are stored per site in POA system database in the apacheh2e_ws_limits_ table and in the Configuration Database in the vapache_h2e_websites_ table.
To see current website limits run the following SQL query in Configuration Database:
select max_conn, ws_rate, cpu_lim, mem_lim, nproc_lim, lve_cpu_lim, lve_nproc_lim from v_apache_h2e_websites; -[ RECORD 1 ]-+-- max_conn | 0 ws_rate | 0 cpu_lim | 0 mem_lim | 0 nproc_lim | 0 lve_cpu_lim | 0 lve_nproc_lim | 0
Request rate and bandwidth are throttled in Apache modules.
lvectl, lveps, lvetop utilities to get information about LVEs on NG
Error messages (if any) may be found in
/etc/httpd/logs/error_log on web servers.
Refer to http://www.cloudlinux.com/docs/workingwithlve.php for more information about LVE technology.
See the main Knowledgebase article #114326 Linux Shared Hosting NG: General Information, Best Practices and Troubleshooting for more information about NG Hosting in Parallels Automation.