English
English
PHP-FPM (PHP FastCGI Process Manager) is a crucial component in the PHP environment, responsible for managing the processes that handle PHP scripts. Unlike traditional thread-based models, PHP-FPM uses a process-based model, where each request is handled by an independent PHP-FPM process. This model improves concurrency and stability.
PHP-FPM can operate independently of web servers (such as Nginx or Apache) and communicates with them through the FastCGI protocol. It automatically adjusts the number of processes based on the configuration file to handle varying load levels.
max_children is an important configuration option in PHP-FPM that defines the maximum number of PHP-FPM processes. Each PHP-FPM process consumes memory and CPU resources, so setting the correct value for max_children is essential for system performance and stability.
If max_children is set too low, requests may queue up, leading to increased response time. On the other hand, setting it too high may cause memory exhaustion, which can degrade performance or even cause the system to crash.
Before adjusting max_children, it’s important to first understand the available resources on the server, such as memory and CPU cores. Tools like top or htop can help monitor resource usage.
Let’s assume the server has 8GB of RAM and 4 CPU cores.
Each PHP-FPM process consumes a certain amount of memory, depending on the complexity and quality of the PHP application. Suppose each process uses around 200MB of memory. For an 8GB server, we can calculate the maximum number of processes as 8GB / 200MB = 40. However, the system also needs some memory for other processes, so we should leave, for example, 2GB for system use. This leaves 6GB for PHP-FPM processes.
If we assume that CPU usage per process is not a major concern, we can allow each PHP-FPM process to use one CPU core. Therefore, max_children can be set to 4, which matches the number of CPU cores.
To modify the max_children value, you need to edit the PHP-FPM configuration file, typically located at /etc/php-fpm.conf or /etc/php/7.4/fpm/php-fpm.conf.
Find the max_children option in the configuration file and set it to the calculated value, for example:
pm.max_children = 4After making the changes, save the configuration file and restart the PHP-FPM service to apply the changes.
Adjusting max_children is just part of the optimization process. Ongoing monitoring and tuning are essential to ensure continued system stability and performance.
You can use tools like top, htop, or the PHP-FPM built-in php-fpm-status page to monitor the state of PHP-FPM processes. These tools allow you to view the current number of PHP-FPM processes, memory usage, and other details, helping you spot issues early and take corrective action.
If you find that the number of PHP-FPM processes is insufficient to handle the current traffic, you may need to increase max_children. Conversely, if the system is running low on memory or the load is too high, you might want to reduce the value. Based on actual request volumes and response times, you can also adjust other relevant PHP-FPM configurations like pm.max_requests and pm.start_servers to achieve better performance.
Be cautious when adjusting max_children. Both too high and too low of a value can cause problems. It’s recommended to perform thorough testing and evaluation before making changes.
Additionally, if there are other non-PHP processes running on the server, their resource usage should also be taken into account to avoid impacting PHP-FPM's performance.
By properly adjusting the max_children configuration in PHP-FPM, you can significantly improve the stability and performance of your server. The correct value depends on your server’s hardware resources and expected traffic load. Regular monitoring and tuning will help maintain optimal system performance.
