Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:php:enable_opcode_cache [2018/08/07 15:00] Lisa Clarke Proofreading |
litespeed_wiki:php:enable_opcode_cache [2018/09/13 20:42] Michael Alegre [For Shared Hosting Environments:PHP SuEXEC] Updated 'Auto Start' setting name to 'Start By Server'. |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| 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: | 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: | ||
| - | Set Auto Start to "Yes". | + | Set Start By Server to "Yes". |
| Set Run On Start Up to "suEXEC Daemon". | Set Run On Start Up to "suEXEC Daemon". | ||
| Line 36: | Line 36: | ||
| === 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. | 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. | ||
| + | |||
| + | 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. | ||
| === Sharing Opcode Cache Between Multiple CPU Processes === | === Sharing Opcode Cache Between Multiple CPU Processes === | ||