cPanel :: Feature Request :: FastCGI Process Manager (FPM) SAPI
Hello,
I think many people who worked with the panel know that without castilla, do not install mod_fastcgi + php-fpm.
It seems to me that if everyone comes to Habra and leaves his vote in support of the implementation of this functionality, then the developers will also not be able to leave this unattended and include it in the standard set.
features.cpanel.net/responses/fastcgi-process-manager-fpm-sapi
FastCGI Process Manager (FPM)
')
FPM (FastCGI Process Manager) is an alternative implementation of PHP FastCGI with several additional features commonly used for heavily loaded sites.
These features include:
A small wiki for those who do not understand what is happening here:
Handler - why do I need it:
In order to run a website in PHP, the server must interpret the PHP code. It interprets the code based on the PHP library you are using, for example PHP 5. The PHP handler is what actually loads the libraries so that they can be used for interpretation. PHP handlers determine how PHP is loaded on the server.
What PHP handlers are available in cPanel:
There are several different handlers that can be used to load PHP: CGI, DSO, suPHP, and FastCGI. Each handler uses a different PHP download implementation. Each implementation affects the performance of the Apache server, because it determines how Apache serves PHP.
So what??
List of PHP handlers:
DSO is also known as mod_php. DSO stands for: Dynamic Shared Object. It is old, but is generally considered the fastest handler. It works as an Apache module. This means that PHP scripts will be executed as an Apache user who is a user: "nobody".
DSO has two drawbacks:
Firstly, all files created using the PHP script will have the owner “nobody”. It will not be available from the Internet. Sites that need to upload files using PHP may have problems with file permissions. This is a WordPress problem, uploading files through the WordPress interface or using the automatic update feature will fail with the DSO.
The second disadvantage is the security issue. The files created will have the owner nobody. If a hacker finds a vulnerability in your PHP script, he could modify or use a file that has the same privileges, important system files, which also belong to nobody.
CGI stands for: Common Gateway Interface. The CGI handler will handle PHP as a CGI module, unlike the Apache module. However, if you have suExec, this will allow you to see which user made the request.
The CGI method is intended as a fallback when the DSO handler is not available. According to cPanel’s own documentation, this method is neither fast nor safe, regardless of whether suExec is enabled or not.
suPHP is read as Single user PHP. suPHP also runs PHP as a CGI module, not an Apache module. It differs from CGI in that PHP scripts that are invoked from the web will run under the user who owns them. suPHP is usually the default handler and Cpanel is recommended for PHP maintenance.
BUT, there is one BUT:
The disadvantage of suPHP is that it creates a much higher load on the processor. In addition, with suPHP, you cannot use code caching (for example, eAccelerator or APC). What creates additional load and slows down the processing speed.
how could they use it by default with the main handler ??????
FCGI (otherwise: mod_fcgid) is a high performance update / CGI variant. It has the advantages of suPHP. The difference with FCGI is that it can significantly save on processor performance and give speeds close to DSO.
The disadvantage of FCGI is (literally):
There is no need for a mod_fcgid case. processes. This means that using the PHP_fcgid process you need to have many PHP processes.
bugs.debian.org/cgi-bin/bugreport.cgi?bug=504132#25
In general terms, the same shit as the previous ones, creates a huge number of separate processes, which, while keeping the cache code separately each in itself, and even die.
read and keywords about what you need to implement.
real FastCGI mod_fastcgi! = mod_fcgid
www.fastcgi.com/drupal/node/6
php-fpm
php-fpm.org/about
I think many people who worked with the panel know that without castilla, do not install mod_fastcgi + php-fpm.
It seems to me that if everyone comes to Habra and leaves his vote in support of the implementation of this functionality, then the developers will also not be able to leave this unattended and include it in the standard set.
features.cpanel.net/responses/fastcgi-process-manager-fpm-sapi
FastCGI Process Manager (FPM)
')
FPM (FastCGI Process Manager) is an alternative implementation of PHP FastCGI with several additional features commonly used for heavily loaded sites.
These features include:
- advanced process management with a correct (graceful) stop and start procedure;
- the ability to run vorkerov with different uid / gid / chroot-environment, as well as running on different ports using different php.ini (replacement safe_mode);
- standard output streams (stdout) and errors (stderr);
- emergency restart in case of sudden destruction of the opcode cache;
- support for accelerated upload;
- “Slowlog” - logging of unusually slow-running scripts (not only their names, but also their tracing. This is achieved using ptrace and other similar utilities for reading execution data of remote processes);
- fastcgi_finish_request () is a special function to complete the request and flush all data buffers, and the process can continue to perform any long-term actions (video conversion, statistics processing, etc.);
- The type of child process launch - dynamic, static and on-demand;
- Basic information about the status of SAPI (similar to Apache mod_status);
- A configuration file based on php.ini.
A small wiki for those who do not understand what is happening here:
Handler - why do I need it:
In order to run a website in PHP, the server must interpret the PHP code. It interprets the code based on the PHP library you are using, for example PHP 5. The PHP handler is what actually loads the libraries so that they can be used for interpretation. PHP handlers determine how PHP is loaded on the server.
What PHP handlers are available in cPanel:
There are several different handlers that can be used to load PHP: CGI, DSO, suPHP, and FastCGI. Each handler uses a different PHP download implementation. Each implementation affects the performance of the Apache server, because it determines how Apache serves PHP.
So what??
List of PHP handlers:
DSO (mod_php)
DSO is also known as mod_php. DSO stands for: Dynamic Shared Object. It is old, but is generally considered the fastest handler. It works as an Apache module. This means that PHP scripts will be executed as an Apache user who is a user: "nobody".
DSO has two drawbacks:
Firstly, all files created using the PHP script will have the owner “nobody”. It will not be available from the Internet. Sites that need to upload files using PHP may have problems with file permissions. This is a WordPress problem, uploading files through the WordPress interface or using the automatic update feature will fail with the DSO.
The second disadvantage is the security issue. The files created will have the owner nobody. If a hacker finds a vulnerability in your PHP script, he could modify or use a file that has the same privileges, important system files, which also belong to nobody.
CGI
CGI stands for: Common Gateway Interface. The CGI handler will handle PHP as a CGI module, unlike the Apache module. However, if you have suExec, this will allow you to see which user made the request.
The CGI method is intended as a fallback when the DSO handler is not available. According to cPanel’s own documentation, this method is neither fast nor safe, regardless of whether suExec is enabled or not.
suPHP
suPHP is read as Single user PHP. suPHP also runs PHP as a CGI module, not an Apache module. It differs from CGI in that PHP scripts that are invoked from the web will run under the user who owns them. suPHP is usually the default handler and Cpanel is recommended for PHP maintenance.
BUT, there is one BUT:
The disadvantage of suPHP is that it creates a much higher load on the processor. In addition, with suPHP, you cannot use code caching (for example, eAccelerator or APC). What creates additional load and slows down the processing speed.
how could they use it by default with the main handler ??????
FCGI
FCGI (otherwise: mod_fcgid) is a high performance update / CGI variant. It has the advantages of suPHP. The difference with FCGI is that it can significantly save on processor performance and give speeds close to DSO.
The disadvantage of FCGI is (literally):
There is no need for a mod_fcgid case. processes. This means that using the PHP_fcgid process you need to have many PHP processes.
bugs.debian.org/cgi-bin/bugreport.cgi?bug=504132#25
In general terms, the same shit as the previous ones, creates a huge number of separate processes, which, while keeping the cache code separately each in itself, and even die.
read and keywords about what you need to implement.
real FastCGI mod_fastcgi! = mod_fcgid
www.fastcgi.com/drupal/node/6
php-fpm
php-fpm.org/about
Source: https://habr.com/ru/post/186498/
All Articles