Private
Server IP : 195.201.23.43  /  Your IP : 3.15.143.178
Web Server : Apache
System : Linux webserver2.vercom.be 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64
User : kdecoratie ( 1041)
PHP Version : 7.1.33-63+ubuntu20.04.1+deb.sury.org+1
Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/webmin/virtual-server/help/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ HOME SHELL ]     

Current File : /usr/share/webmin/virtual-server/help/phpmode_fpmtype.html
<header>PHP process manager mode</header>
PHP-FPM, or FastCGI Process Manager for PHP, provides several management
modes for its worker processes. These modes determine how PHP-FPM will
create, maintain, and recycle the child processes that handle PHP requests.
The mode is set using the <tt>pm</tt> configuration directive.<br>

<br>
<b><tt>dynamic</tt></b> (default)<br>
In the <tt>dynamic</tt> mode, PHP-FPM dynamically adjusts the number of spawned
child processes based on the demand, and controlled by the following directives:
<p></p>
<table>
<tr>
        <td style="white-space: nowrap; vertical-align: top; padding-right: 0.5rem!important;"><tt>pm.max_children</tt></td>
        <td>the maximum number of children that can be alive at the same time</td>
</tr>
<tr>
        <td style="white-space: nowrap; vertical-align: top; padding-right: 0.5rem!important;"><tt>pm.start_servers</tt></td>
        <td>the number of children created on startup</td>
</tr>
<tr>
        <td style="white-space: nowrap; vertical-align: top; padding-right: 0.5rem!important;"><tt>pm.min_spare_servers</tt></td>
        <td>the minimum number of children in 'idle' state (waiting to process). If the number of 'idle' processes is less than 
                this number then some children will be created</td>
</tr>
<tr>
        <td style="white-space: nowrap; vertical-align: top; padding-right: 0.5rem!important;"><tt>pm.max_spare_servers</tt></td>
        <td>the maximum number of children in 'idle' state (waiting to process). If the number of 'idle' processes is greater than 
                this number then some children will be killed</td>
</tr>
<tr>
        <td style="white-space: nowrap; vertical-align: top; padding-right: 0.5rem!important;"><tt>pm.max_spawn_rate</tt></td>
        <td>the maximum number of rate to spawn child processes at once</td>
</tr>
</table>  
<p></p>
Benefits include automatic adjustment
of the number of child processes based on demand, ensuring optimal resource
utilization. This is especially useful for servers with fluctuating loads.<br>

<br>
<b><tt>static</tt></b><br>
In the <tt>static</tt> mode, PHP-FPM maintains a fixed number of child processes.
This number is specified by the <tt>pm.max_children</tt> directive. Benefits include
consistent memory usage due to a constant number of child processes. This is ideal
for servers with stable loads.<br>

<br>
<b><tt>ondemand</tt></b><br>
In the <tt>ondemand</tt> mode, no children are created at startup. Instead PHP-FPM will spawn child processes only when needed,
i.e., when there's an incoming request that needs processing. The maximum number of children that can be alive at the same time
is controlled by <tt>pm.max_children</tt> directive. Processes are then terminated after being idle for a specified amount of
time by the <tt>pm.process_idle_timeout</tt> directive. Benefits include reduced memory usage during periods of low or no traffic.
Ideal for servers with intermittent loads or applications with unpredictable traffic
patterns.<br>

<br>
The best mode for your application may vary based on the server's available resources, traffic
patterns, and specific application characteristics. It's essential to monitor and fine-tune the
settings to achieve optimal performance.
<footer>

Private