Differences

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

--- litespeed_wiki:php:enable_opcode_cache [2018/08/07 14:34]
Jackson Zhang [For shared hosting environments:PHP SuEXEC]
+++ litespeed_wiki:php:enable_opcode_cache [2018/08/07 18:30]
Jackson Zhang [For Shared Hosting Environments:PHP SuEXEC]
@@ Line 1: / Line 1: @@
-====== Enable PHP opcode cache for LiteSpeed ======
+====== Enable PHP Opcode Cache for LiteSpeed ======
-===== Choosing an opcode cache =====
+===== Choosing an Opcode Cache =====
 Since PHP 5.5, Zend Opcode Cache has been included in the PHP main package distribution and can be easily installed through yum or apt-get. For PHP 5.4 and lower, you can use [[litespeed_wiki:php:apc|APC cache]]. APC cache already includes PHP opcode cache and user cache. To use user/variable cache for PHP 5.5 and up with Zend Opcode cache only, you may also add apcu.
@@ Line 7: / Line 7: @@
 Xcache may also be used with PHP up to version 5.6, but not 7.0.
-===== How to enable opcode cache for LiteSpeed =====
+===== 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.
-==== For shared hosting environments:PHP SuEXEC ====
+==== For Shared Hosting Environments:PHP SuEXEC ====
 For shared hosting environments such as cPanel or Plesk, you should use the PHP SuEXEC mode. 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.
@@ Line 18: / Line 18: @@
 You may follow [[litespeed_wiki:php:which_php_setup_am_i_using#which_suexec_mode_am_i_using|this wiki]] to check which SuEXEC mode you are using. suEXEC Daemon Mode and suEXEC ProcessGroup Mode support opcode cache while the default suEXEC Worker Mode does not. If using opcode cache, you will need to change to suEXEC Daemon Mode or suEXEC ProcessGroup Mode.
-=== How to setup suEXEC Daemon mode ===
+=== How to Set up suEXEC Daemon Mode ===
 To set up suEXEC Daemon mode, you need only adjust your server-level LSPHP external application settings in the WebAdmin console > Configuration > External App > your LSPHP external application:
@@ Line 24: / Line 24: @@
   Set Run On Start Up to "suEXEC Daemon".
-=== How to setup ProcessGroup mode ===
+=== How to Set up ProcessGroup Mode ===
 To set up ProcessGroup, you need to place the directive LSPHP_ProcessGroup in an httpd.conf file. This can be done at the server or virtual host level. If done at the server level, all virtual hosts will use ProcessGroup. If done at the virtual host level, only that virtual host will use ProcessGroup.
@@ Line 34: / Line 34: @@
   </IfModule>
-=== ProcessGroup mode vs PHP-FPM ===
+=== 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.
-=== Does opcode cache shared between multi-core processes? ===
+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.
-For LSWS 2CPU and above licenses, you have an option to [[litespeed_wiki:cpanel:multi-litespeed-processes|configure LSWS to use multi CPU cores]]. For LSWS 5.2.x and below, When a domain served by multi-CPU cores, Opcache cache cannot be shared between CPU cores.  So when you test a phpinfo.php page, you might see cache hits like the following when refreshing a phpinfo.php page.
+=== Sharing Opcode Cache Between Multiple CPU Processes ===
+For LSWS 2CPU and above licenses, you have an option to [[litespeed_wiki:cpanel:multi-litespeed-processes|configure LSWS to use multi CPU cores]]. For LSWS 5.2.x and below, When a domain is served by multi-CPU cores, Opcode cache cannot be shared between CPU cores.  So, when you test a ''phpinfo.php'' page, you might see cache hits like the following upon refresh:
   http://example.com/phpinfo.php
@@ Line 49: / Line 52: @@
-From LSWS 5.3RC2 and above version, LSWS can share opcache between Multi CPU processes.
+As of LiteSpeed Web Server v5.3RC2 and above, LSWS //can share opcache between Multi CPU processes//.
-==== For non-shared hosting environments:PHP non-SuEXEC ====
+==== For Non-Shared Hosting Environments:PHP non-SuEXEC ====
-Non-shared hosting environments should use PHP non-exec mode. (LSWS Web Admin -> Server -> General -> Using Apache Configuration File -> PHP suEXEC -> No). LSPHP just runs in ''workgroup'' mode as the "nobody" user by default. For this situation, as long as you see opcode cache in the phpinfo page, opcode cache has already been enabled.
+Non-shared hosting environments should use PHP non-exec mode. (**LSWS Web Admin > Server > General > Using Apache Configuration File > PHP suEXEC** = ''No''). LSPHP just runs in ''workgroup'' mode as the "nobody" user by default. For this situation, as long as you see opcode cache in the phpinfo page, opcode cache has already been enabled.
 More details about [[litespeed_wiki:php:which_php_setup_am_i_using|PHP SuEXEC or non-SuEXEC here]].