Differences and optimization techniques in the PHP-FPM configuration file /etc/php/8.3/fpm/pool.d/

Is everything alright once the server is running? Actually, in the world of PHP-FPM, the configuration file is the real mastermind, determining whether the site can run stably, securely, and efficiently.

What is the process pool configuration for PHP-FPM?

PHP-FPM (FastCGI Process Manager) is a process manager for PHP that uses the concept of "pools" to manage PHP processes for different websites or applications.

Every .conf The file is a pool definition that specifies key parameters such as the user on which the process runs, the port or socket it listens on, the log path, and the number of processes.

In other words, these files are like "clones" for your server, allowing different sites to run independently without interfering with each other.

http://www.conf：默认的进程池

After installing PHP-FPM, the system will automatically generate a www.conf file.

Its function is to provide a default pool that works out of the box, typically running in... www-data User.

This pool is suitable for single-site environments, is easy to configure, and most of the parameters are generic values, such as:

• user = www-data
• group = www-data
• listen = /run/php/php8.3-fpm.sock
• pm.max_children = 5

If you're only running on one site, this is sufficient.

etUFO.org.conf: Custom site pool

When you have multiple sites, you need to create a separate pool for each site.

such as etufo.org.confIt is specifically for domain names. etUFO.org Exclusive configuration.

The common practice is:

• Specify different users and groups, for example user = etufo.group = etufo
• Configure a separate listening port or socket, for example listen = /run/php/etufo.sock
• Adjust the number of processes to ensure site stability under high concurrency.
• Independent log files facilitate troubleshooting.

The advantage of this approach is security isolation: even if one site is attacked, other sites will not be affected.

dummy.conf: Example or placeholder file

dummy.conf These are usually templates or examples provided by the system.

It will not be actually enabled unless you manually modify and enable it.

Its purpose is to provide you with a reference and show you how to write a new pool configuration.

Therefore, it is more like an "instruction manual" than an actual configuration for operation.

Why use multiple pool files?

• SafetyDifferent sites should be run by different users to avoid overlapping permissions.
• Performance optimizationThe number of processes can be set individually for each pool and adjusted according to traffic demand.
• IsolationLogs, error output, and listening ports are all separated, making troubleshooting easier.

For example, if www.conf It collapsed.etufo.org.conf It can still run normally and will not bring down the entire server.

Actual application scenarios

• Single-site serverOnly use www.conf That's enough.
• Multisite server: Build one for each site .conf Files, such as etufo.org.conf.
• dummy.confFor reference only, not recommended.

Configuration Comparison Example

http://www.conf（默认池）

[www]
user = www-data
group = www-data
listen = /run/php/php8.3-fpm.sock
pm = dynamic
pm.max_children = 5

etufo.org.conf (Custom Pool)

[etufo.org]
user = etufo
group = etufo
listen = /run/php/etufo.sock
pm = dynamic
pm.max_children = 20
access.log = /var/log/php-fpm/etufo.access.log

You'll find that the difference lies in the user, the listening address, and the number of processes.

Adjusting PHP-FPM process pool parameters

If the configuration uses dynamicThis is a method of pre-starting some work processes and dynamically adjusting them according to the request volume, which can respond faster when the request volume suddenly increases.

For websites with a certain amount of traffic, it is recommended to use pm = dynamicBecause it can maintain a certain amount of idle processes and avoid 500 errors during high concurrency.

It is recommended to use it only when the access volume is extremely low and the memory resources are tight. pm = ondemand To save resources.

It is recommended to change it to dynamic and optimize it. pm.max_children And other parameters:

pm = dynamic
pm.max_children = 16  ; 根据服务器资源调整，建议值：CPU 核心数 × 2
pm.start_servers = 4   ; 初始进程数，建议设为 max_children × 25%
pm.min_spare_servers = 2  ; 最小空闲进程数
pm.max_spare_servers = 7  ; 最大空闲进程数
pm.max_requests = 3000    ; 每个子进程处理完 3000 个请求后自动重启
pm.process_idle_timeout = 10s  ; 空闲进程 10s 后自动退出

This configuration ensures performance while avoiding resource waste.

For detailed configuration instructions, please refer to the following tutorial ▼

🔗HestiaCP PHP-FPM is overloaded? Dynamic web pages have 500 errors? This optimization will take effect immediately!

According to the official PHP documentation:

“Each pool can be configured independently, allowing for different users, limits, and settings per application.”

This statement clearly points out the significance of multi-pool configuration: independence, flexibility, and controllability.

Conclusion: My Viewpoint

Server configuration is like a conductor in an orchestra, determining how each instrument should be played.

www.conf It is the default conductor, suitable for solo performances;etufo.org.conf It is a conductor tailor-made for a specific stage; and dummy.conf It is a draft of musical scores, reminding you how to write new melodies.

In an era focused on information security and performance optimization, knowing how to properly use these configuration files is key to controlling the lifeline of a server.

Configuration is not just trivial text; it is the soul of a server.

If you are operatingWordpressFor multi-site applications, we strongly recommend that you immediately check and optimize these pool files, especially the process pool parameter settings, to make your server truly rock-solid.