php-fpm static dynamic

This article mainly introduces the static and dynamic aspects of php-fpm. Now I will share it with you and give you a reference. Let’s take a look together

php-fpmstaticstaticanddynamicdynamicComparison of execution methods
When configuring php-fpm some time ago, I accidentally discovered It turns out that he has two other ways of execution. Like Apache, its number of processes can also be divided into dynamic and static according to settings.
There are also two ways for php-fpm. One is to directly open a specified number of php-fpm processes without increasing or decreasing them; the other is to open a certain number of php-fpm processes at the beginning. When the request volume becomes large, the number of php-fpm processes is dynamically increased to the upper limit, and when idle, the number of idle processes is automatically released to a lower limit.
These two different execution methods can be adjusted according to the actual needs of the server.
Let’s first talk about several parameters involved in this. They are pm, pm.max_children, pm.start_servers, pm.min_spare_servers and pm.max_spare_servers.
pm indicates which method to use. There are two values ​​to choose from, namely static (static) or dynamic (dynamic). In older versions, dynamic was called apache-like. Please pay attention to the instructions given in the configuration file.
The following four parameters mean:

1. pm.max_children: The number of php-fpm processes opened in static mode.

2. pm.start_servers: The number of starting php-fpm processes in dynamic mode.

3. pm.min_spare_servers: The minimum number of php-fpm processes in dynamic mode.

4. pm.max_spare_servers: The maximum number of php-fpm processes in dynamic mode.

If dm is set to static, then only the pm.max_children parameter will take effect. The system will open the set number of php-fpm processes.
If dm is set to dynamic, then the pm.max_children parameter will be invalid and the next three parameters will take effect. The system will start pm.start_servers php-fpm processes when php-fpm starts running, and then dynamically adjust the number of php-fpm processes between pm.min_spare_servers and pm.max_spare_servers according to the needs of the system.
So, which execution method is better for our server? In fact, like Apache, the PHP program we run will more or less have memory leaks after execution. This is also the reason why a php-fpm process only occupies about 3M of memory at the beginning, and it will increase to 20-30M after running for a period of time. Therefore, the dynamic method will end redundant processes and can recycle and release some memory, so it is recommended to be used on servers or VPS with less memory. The specific maximum amount is obtained based on memory/20M. For example, for a 512M VPS, it is recommended to set pm.max_spare_servers to 20. As for pm.min_spare_servers, it is recommended to set it according to the load of the server. A more suitable value is between 5 and 10.
Then for servers with relatively large memory, setting it to static will improve efficiency. Because frequent switching of the php-fpm process will cause lag, so if the memory is large enough, the static effect will be better. The quantity can also be obtained according to memory/30M. For example, a server with 2GB memory can be set to 50; a server with 4GB memory can be set to 100, etc.
This site is built on a 512M VPS, so the parameters I set are as follows:
pm=dynamic
pm.max_children=20
pm.start_servers=5
pm.min_spare_servers=5
pm.max_spare_servers=20
This can save memory to the greatest extent and improve execution efficiency.
Attached are the descriptions of each parameter:
pm string
Set how the process manager manages child processes. Available values: static, ondemand, dynamic. Must be set.
static - The number of child processes is fixed (pm.max_children).
ondemand - The process is spawned when there is demand (when requested, contrary to dynamic, pm.start_servers is started when the service starts.
dynamic - The number of child processes is dynamically set based on the following configuration: pm .max_children, pm.start_servers, pm.min_spare_servers, pm.max_spare_servers.
pm.max_children int
When pm is set to static, it indicates the number of child processes created. When pm is set to dynamic, it indicates the maximum number of child processes that can be created. The number. Must be set.
This option sets the limit on the number of requests that can be served at the same time. Similar to the setting of MaxClients in Apache's mpm_prefork and the PHP_FCGI_CHILDREN environment variable in ordinary PHP FastCGI
Set startup. The number of child processes created. Only used when pm is set to dynamic. Default value: min_spare_servers (max_spare_servers - min_spare_servers) / 2.
pm.min_spare_servers int
Set the minimum number of idle service processes only. Used when dynamic. Must be set.
pm.max_spare_servers int
Set the maximum number of idle service processes. Must be set when pm is set to dynamic. The number of requests served before the child process is reborn. This is useful for third-party modules that may have memory leaks. If set to '0', it will always accept requests, which is equivalent to the PHP_FCGI_MAX_REQUESTS environment variable.

php-fpm
staticstatic

and

dynamicdynamicComparison of execution methodsWhen configuring php-fpm some time ago, I accidentally discovered that it has two execution methods . Like Apache, the number of its processes can also be divided into dynamic and static according to the settings. There are also two ways for php-fpm. One is to directly open the specified number of php-fpm processes without increasing it. Or reduce; the other is to start a certain number of php-fpm processes at the beginning. When the request volume becomes large, dynamically increase the number of php-fpm processes to the upper limit, and automatically release the idle processes when they are idle. The number of idle processes reaches one. lower limit. These two different execution methods can be adjusted according to the actual needs of the server.
Let’s first talk about several parameters involved in this. They are pm, pm.max_children, pm.start_servers, pm.min_spare_servers and pm.max_spare_servers.
pm indicates which method to use. There are two values ​​to choose from, namely static (static) or dynamic (dynamic). In older versions, dynamic was called apache-like. Please pay attention to the instructions given in the configuration file.
The following four parameters mean:

pm.max_children: The number of php-fpm processes opened in static mode.

1. pm.start_servers: The number of starting php-fpm processes in dynamic mode.

2. pm.min_spare_servers: The minimum number of php-fpm processes in dynamic mode.

3. pm.max_spare_servers: The maximum number of php-fpm processes in dynamic mode.

If dm is set to static, then only the pm.max_children parameter will take effect. The system will open the set number of php-fpm processes.
If dm is set to dynamic, then the pm.max_children parameter will be invalid and the next three parameters will take effect. The system will start pm.start_servers php-fpm processes when php-fpm starts running, and then dynamically adjust the number of php-fpm processes between pm.min_spare_servers and pm.max_spare_servers according to the needs of the system.
So, which execution method is better for our server? In fact, like Apache, the PHP program we run will more or less have memory leaks after execution. This is also the reason why a php-fpm process only occupies about 3M of memory at the beginning, and it will increase to 20-30M after running for a period of time. Therefore, the dynamic method will end redundant processes and can recycle and release some memory, so it is recommended to be used on servers or VPS with less memory. The specific maximum amount is obtained based on memory/20M. For example, for a 512M VPS, it is recommended to set pm.max_spare_servers to 20. As for pm.min_spare_servers, it is recommended to set it according to the load of the server. A more suitable value is between 5 and 10.
Then for servers with relatively large memory, setting it to static will improve efficiency. Because frequent switching of the php-fpm process will cause lag, so if the memory is large enough, the static effect will be better. The quantity can also be obtained according to memory/30M. For example, a server with 2GB memory can be set to 50; a server with 4GB memory can be set to 100, etc.
This site is built on a 512M VPS, so the parameters I set are as follows:
pm=dynamic
pm.max_children=20
pm.start_servers=5
pm.min_spare_servers=5
pm.max_spare_servers=20
This can save memory to the greatest extent and improve execution efficiency.
Attached are the descriptions of each parameter:
pm string
Set how the process manager manages child processes. Available values: static, ondemand, dynamic. Must be set.
static - The number of child processes is fixed (pm.max_children).
ondemand - The process is spawned when there is demand (when requested, contrary to dynamic, pm.start_servers is started when the service starts.
dynamic - The number of child processes is dynamically set based on the following configuration: pm .max_children, pm.start_servers, pm.min_spare_servers, pm.max_spare_servers.
pm.max_children int
When pm is set to static, it indicates the number of child processes created. When pm is set to dynamic, it indicates the maximum number of child processes that can be created. The number. Must be set.
This option sets the limit on the number of requests that can be served at the same time. Similar to the setting of MaxClients in Apache's mpm_prefork and the PHP_FCGI_CHILDREN environment variable in ordinary PHP FastCGI
Set startup. The number of child processes created. Only used when pm is set to dynamic. Default value: min_spare_servers (max_spare_servers - min_spare_servers) / 2.
pm.min_spare_servers int
Set the minimum number of idle service processes only. Used when dynamic. Must be set.
pm.max_spare_servers int
Set the maximum number of idle service processes. Must be set when pm is set to dynamic. The number of requests served before the child process is reborn. This is useful for third-party modules that may have memory leaks. If set to '0', it will always accept requests, which is equivalent to the PHP_FCGI_MAX_REQUESTS environment variable.

Related recommendations:

php-fpm pool, PHP slow execution log, open_basedir, php-fpm process management

php-fpm restart

The above is the detailed content of php-fpm static dynamic. For more information, please follow other related articles on the PHP Chinese website!