Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
litespeed_wiki:php:process-mode [2018/09/21 17:36]
Michael Alegre [Limitations]
litespeed_wiki:php:process-mode [2018/09/24 18:08]
Michael Alegre [Benefits]
Line 35: Line 35:
 </​code>​ </​code>​
  
-Note the two LiteSpeed-specific directives ''​[[litespeed_wiki:​php:​lsapi-environment-variables#​lsphp_processgroup|LSPHP_ProcessGroup]]''​ and ''​[[litespeed_wiki:​php:​lsapi-environment-variables#​lsphp_workers|LSPHP_Workers]]''​. Apache will not understand these directives and may crash if it encounters outside of by an ''<​IfModule LiteSpeed>''​ block.+Note the two LiteSpeed-specific directives ''​[[litespeed_wiki:​php:​lsapi-environment-variables#​lsphp_processgroup|LSPHP_ProcessGroup]]''​ and ''​[[litespeed_wiki:​php:​lsapi-environment-variables#​lsphp_workers|LSPHP_Workers]]''​. Apache will not understand these directives and may crash if it encounters ​them outside of by an ''<​IfModule LiteSpeed>''​ block.
  
 ==== Configuration tips ==== ==== Configuration tips ====
Line 77: Line 77:
 ==== Benefits ==== ==== Benefits ====
   * Worker mode is compatible with custom php.ini files including CloudLinux’s CageFS php.ini files, allowing the use of CloudLinux'​s PHP Selector. ​   * Worker mode is compatible with custom php.ini files including CloudLinux’s CageFS php.ini files, allowing the use of CloudLinux'​s PHP Selector. ​
-  * When running PHP using a suEXEC execution method, ​Worker mode conserves resources by killing idle processes. ​This is more efficient than Apache + PHP-FPM where at least one process is always running in each user's pool.  ​+ Worker mode conserves resources by killing idle processes. ​When running PHP using a suEXEC execution method, this is more efficient than Apache + PHP-FPM where at least one process is always running in each user's pool.  ​
  
 ==== Limitations ==== ==== Limitations ====
Line 84: Line 84:
  
 ==== Setup ==== ==== Setup ====
-Worker mode will be used when none the setting requirements for [[#​processgroup_mode|ProcessGroup mode]] (default) or [[#​daemon_mode|Daemon mode]] have been met. LiteSpeed Web Server may also automatically switch to Worker mode at the Server level if a custom php.ini file is detected when running in [[#​daemon_mode|Daemon mode]].+LiteSpeed Web Server will use Worker mode when none of the setting requirements for [[#​processgroup_mode|ProcessGroup mode]] (default) or [[#​daemon_mode|Daemon mode]] have been met. LiteSpeed Web Server may also automatically switch to Worker mode at the Server level if it detects ​a custom php.ini file while running in [[#​daemon_mode|Daemon mode]].
  
 ===== Mode Comparison ===== ===== Mode Comparison =====
Line 92: Line 92:
 ^ Number of parent processes ​                       |  One for each process group\\ (each user)  |  1  |  0  | ^ Number of parent processes ​                       |  One for each process group\\ (each user)  |  1  |  0  |
 ^ Customize number of processes per account? |  Yes  |  Yes  |  Yes  | ^ Customize number of processes per account? |  Yes  |  Yes  |  Yes  |
-^ Can be enabled ​only for certain virtual hosts? |  Yes  |  No  |  No  |+^ Can enable ​only for certain virtual hosts? |  Yes  |  No  |  No  |
 ^ Custom php.ini supported? (Including CageFS custom php.ini) |  Yes  |  No  |  Yes  | ^ Custom php.ini supported? (Including CageFS custom php.ini) |  Yes  |  No  |  Yes  |
 ^ Opcode caching |  Dedicated per user  |  Shared throughout server ​ |  No  | ^ Opcode caching |  Dedicated per user  |  Shared throughout server ​ |  No  |
  
  • Admin
  • Last modified: 2018/09/24 18:08
  • by Michael Alegre