/ php fpm pool / 300%
PHP-FPM (FastCGI Process Manager) dramatically speeds up the performance
(mod_PHP) PHP-FPM



PHP-FPM

mod_PHP PHP-FPM . . PHP . PHP mod_php. Apache HTTP. . PHP-FPM mod_PHP . PHP-FPM .

PHP-FPM ( FastCGI) PHP .
PHP-FPM vs. mod_PHP Performance Benchmarks

WordPress PHP-FPM mod_PHP PHP-FPM.

Performance with mod_PHP

4 . .



38.046 295.0 7399.11 206219.42 . ​​ 128.0 / 11059200 / .

2150 .

Performance with PHP-FPM

PHP-FPM.



85829 295.0 16465.18 465728.74 . ​​290.0 / 2556000 / .

628 .


PHP-FPM 350% loading times. mod_php PHP-FPM PHP PHP FastCGI . PHP FastCGI.

PHP-FPM pool PHP-FPM PHP . .

PHP-FPM

23 2016 PHP-FPM . mod_PHP . 23 PHP-FPM .

PHP-FPM mod_PHP:

PHP-FPM mod_PHP. : . PHP-FPM . (mod_PHP) PHP-FPM.

-------------------------------------------------

How to Use PHP-FPM with cPanel

PHP performance is an enduring issue for web hosts. PHP is the most widely used server programming language on the web by a big margin. The most popular content management systems and ecommerce applications are written in PHP, including WordPress, Joomla, Drupal, Magento, and dozens more.
The ultra-fast PHP-FPM accelerates PHP execution on busy web servers, making it a valuable tool in the fight against slow sites and resource-constrained servers.
This article takes a deep dive into how PHP-FPM works and explains how to deploy and configure it with cPanel & WHM.
What is PHP-FPM?

PHP-FPM is an alternative PHP implementation that makes busy web applications faster while helping system administrators to control resource consumption on their server.
A PHP implementation, also known as the runtime, interprets and executes code. Traditional runtimes such as Apaches mod_PHP do their work within the web server. That approach has advantages, but each connection consumes a chunk of the servers resources for as long as it lasts. If there are too many concurrent connections, the server may run out of resources like memory altogether, impacting the performance of every site it hosts.
PHP-FPM does things differently: it operates outside of the web server and uses a pool of worker processes to execute code. The workers are ready and waiting when a request comes in, and you can control how many workers are in the pool so they cant multiply until they consume all the servers RAM and processor time.

It works like this:

  • Apache sends code to PHP-FPM over a high-speed binary interface called FastCGI.
  • A supervisor process chooses a worker process from the pool and gives it the code.
  • The worker executes the code, and the result is sent back to Apache, which sends it to the web browser.
  • Once the worker is done, it returns to the pool to await another chunk of code to execute.

If there are too many concurrent connections, some might have to wait for a free worker, but they will never consume all of the servers resources. On a busy web server, worker pools are faster and more efficient than other strategies.
Getting Started with PHP-FPM in CentOS and EasyApache

It is straightforward to activate and configure PHP-FPM in cPanel & WHM. You can choose which domains use it and set configuration variables that influence its behavior.
The first step is to turn it on in the System PHP-FPM settings in WHMs MutliPHP Manager.
When you click Turn On, WHM makes PHP-FPM available, but it doesnt activate it for all domains automatically. You can force all accounts on the server to use PHP-FPM by clicking Convert All Accounts to PHP-FPM.
Alternatively, you can activate PHP-FPM for individual domains in the table at the bottom of this page. To turn it on for several domains at once, select them in the table and choose On in the drop-down menu.
Configuring PHP-FPM in cPanel

Once you have activated PHP-FPM, you can configure both the system defaults and the settings for individual domains in MultiPHP Manager.
Click the System PHP-FPM Configuration tab.
In this section, there are three pool settings you can change. These are the default values that are applied to domain pools.

  • Max Requests: The number of requests each worker process should execute before it restarts itself. This setting is useful for working around memory leaks. The default of 20 is acceptable for most web hosting scenarios, but you may want to increase it to between 40 and 60 on servers with heavy traffic.
  • Process Idle Timeout: How long an idle worker process will wait before shutting down. Idle processes consume resources, so we dont want too many hanging around, but we dont want to kill them too soon because it takes a while to start new ones. The default of 10 (seconds) may be too low for a busy server.
  • Max Children: The maximum number of worker processes in each pool. The default is 5.

Many factors affect the optimal values for these settings, including the code your server runs and the amount of RAM it has. We wrote PHP-FPM Performance Tuning Basicsto help you decide on the correct values for your server.
Underneath the pool options are PHP INI directives. We surface several of the most useful in the interface, and you can find more information about them in PHPs Runtime Configuration documentation. Well show you how to add other directives in the next section.
In addition to system-wide configuration, you can also configure individual domains in the WHM interface.
In the table at the bottom of MutliPHP Manager, click Edit PHP-FPM at the end of the domains row. The options that appear are identical to those in the system-wide configuration interface.