Differences

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

--- litespeed_wiki:php:enable_opcode_cache [2018/09/19 18:32]
Michael Alegre [For Non-Shared Hosting Environments:PHP non-SuEXEC]
+++ litespeed_wiki:php:enable_opcode_cache [2019/05/16 20:21]
Kacey Schroeder [For Shared Hosting Environments: PHP SuEXEC]
@@ Line 13: / Line 13: @@
 ==== 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 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.
+For shared hosting environments such as cPanel or Plesk, you should use PHP SuEXEC mode as your execution method. **Configuration > 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 41: / Line 41: @@
 === 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:
+For LSWS 2-CPU 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