rfc:socketactivation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rfc:socketactivation [2012/10/18 23:50] davidstrauss [Why not just use the ondemand process manager?] |
rfc:socketactivation [2017/09/22 13:28] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * Date: 2012-10-17 | * Date: 2012-10-17 | ||
| * Author: David Strauss <david@davidstrauss.net>, Jerry Blakley <jerry@getpantheon.com> | * Author: David Strauss <david@davidstrauss.net>, Jerry Blakley <jerry@getpantheon.com> | ||
| - | * Status: Under Discussion | + | * Status: Inactive |
| * First Published at: http://wiki.php.net/rfc/socketactivation | * First Published at: http://wiki.php.net/rfc/socketactivation | ||
| * Patches: [[rfc/socketactivation/build.patch|build.patch]] (needs to be made optional), [[rfc/socketactivation/activate.patch|activate.patch]] | * Patches: [[rfc/socketactivation/build.patch|build.patch]] (needs to be made optional), [[rfc/socketactivation/activate.patch|activate.patch]] | ||
| Line 61: | Line 61: | ||
| ==== /etc/php-fpm.d/my-php-fpm-pool.conf ==== | ==== /etc/php-fpm.d/my-php-fpm-pool.conf ==== | ||
| + | |||
| + | It's possible the final implementation may move to "listen = fd:3" or similar syntax to directly request use of an inherited socket rather than requiring a perfect socket configuration match-up between the systemd socket configuration and the PHP-FPM pool configuration. This would make PHP's inheritance more consistent with my nginx proposal. | ||
| <file> | <file> | ||
| Line 88: | Line 90: | ||
| ==== Why not just use the ondemand process manager? ==== | ==== Why not just use the ondemand process manager? ==== | ||
| - | The ondemand process manager still keeps considerable memory allocated, and PHP-FPM currently has some idle CPU load when not processing requests. It's <1% of a core per service, but it adds up when you manage 500+ pools, each as a service for security, on a box. | + | The ondemand process manager still keeps considerable memory allocated, and PHP-FPM currently has some idle CPU load when not processing requests. It's <1% of a core per service, but it adds up when you manage 500+ pools, each as a service for security/resource isolation, on a box. |
| The ondemand process manager doesn't solve the dependency issue mentioned earlier (a web server requiring PHP-FPM to be ready) or allow privileges to be dropped before PHP-FPM gets invoked at all. The latter is useful for platform providers that let users configure PHP-FPM for their individual use cases but want to provide assigned "listening" sockets. | The ondemand process manager doesn't solve the dependency issue mentioned earlier (a web server requiring PHP-FPM to be ready) or allow privileges to be dropped before PHP-FPM gets invoked at all. The latter is useful for platform providers that let users configure PHP-FPM for their individual use cases but want to provide assigned "listening" sockets. | ||
| Line 100: | Line 102: | ||
| ===== Changelog ===== | ===== Changelog ===== | ||
| + | * 2012-11-09: Explain a minor configuration change possibility to harmonize this proposal with the one for nginx. | ||
| * 2012-10-18: Integrate discussion items from the PHP internals list. | * 2012-10-18: Integrate discussion items from the PHP internals list. | ||
| * 2012-10-18: Patches added. | * 2012-10-18: Patches added. | ||
| * 2012-10-17: Initial version. | * 2012-10-17: Initial version. | ||
rfc/socketactivation.1350604240.txt.gz · Last modified: 2017/09/22 13:28 (external edit)