Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:php:enable_opcode_cache [2018/09/14 15:47]
Michael Alegre [For Shared Hosting Environments:PHP SuEXEC]
+++ litespeed_wiki:php:enable_opcode_cache [2018/09/14 16:15]
Michael Alegre [For Shared Hosting Environments:PHP SuEXEC]
@@ Line 9: / Line 9: @@
 ===== How to Enable Opcode Cache for LiteSpeed =====
-Opcode cache can be easily installed through yum or apt-get. To see if it has been enabled, check the corresponding phpinfo page. If you use the PHP non-EXEC mode you may be finished at this point, however when using PHP SuEXEC mode for shared hosting environments such as cPanel or Plesk, you also have to choose the right LSPHP SuEXEC mode.
+Opcode cache can be easily installed through yum or apt-get. To see if it has been enabled, check the corresponding phpinfo page. If you use the PHP non-EXEC mode you may be finished at this point, however when using PHP SuEXEC mode for shared hosting environments such as cPanel or Plesk, you also have to choose the right PHP process mode.
 ==== For Shared Hosting Environments:PHP SuEXEC ====
-For shared hosting environments such as cPanel or Plesk, you should use PHP SuEXEC mode as your execution method. LSWS Web Admin -> Server -> General -> Using Apache Configuration File -> PHP suEXEC -> Yes. When you check a user's phpinfo page, it may show that Zend Opcode Cache is installed and enabled.
+For shared hosting environments such as cPanel or Plesk, you should use PHP SuEXEC mode as your execution method. **LSWS WebAdmin Console -> Server -> General -> Using Apache Configuration File -> PHP suEXEC** to ''Yes''. When you check a user's phpinfo page, it may show that Zend Opcode Cache is installed and enabled.
 However there are also three PHP process modes for LiteSpeed: Worker mode, Daemon mode and ProcessGroup mode.
@@ Line 35: / Line 35: @@
 === ProcessGroup Mode vs. PHP-FPM ===
-Process Group Mode is similar to Apache php-fpm mode. The difference is: with Apache, the parent process of php-fpm is not controlled by Apache, and it keeps running; with LiteSpeed, LiteSpeed uses LSAPI, and the PHP will exit if idle for a while (in a shared hosting environment and set at [[https://www.litespeedtech.com/docs/webserver/config/extapps/lsapi#extMaxIdleTime|"Max Idle time"]]).  For LSWS 5.2.8 and lower versions, PHP processes will stop when LSWS restarts, and the opcode cache will be reset. Starting from LSWS 5.3RC2 and above, LSPHP will run in detached mode and an LSWS restart //won't// stop PHP processes. The LSPHP parent will just follow the timeout where [[https://www.litespeedtech.com/docs/webserver/config/extapps/lsapi#extMaxIdleTime|"Max Idle time"]] is set.
+ProcessGroup Mode is similar to Apache php-fpm mode. The difference is: with Apache, the parent process of php-fpm is not controlled by Apache, and it keeps running; with LiteSpeed, LiteSpeed uses LSAPI, and the PHP will exit if idle for a while (in a shared hosting environment and set at [[https://www.litespeedtech.com/docs/webserver/config/extapps/lsapi#extMaxIdleTime|"Max Idle time"]]).  For LSWS 5.2.8 and lower versions, PHP processes will stop when LSWS restarts, and the opcode cache will be reset. Starting from LSWS 5.3RC2 and above, LSPHP will run in detached mode and an LSWS restart //won't// stop PHP processes. The LSPHP parent will just follow the timeout where [[https://www.litespeedtech.com/docs/webserver/config/extapps/lsapi#extMaxIdleTime|"Max Idle time"]] is set.
 Please keep in mind that keep idle PHP process running longer will occupy server resources and there is a risk to overload the server if there is not enough resources.