What is the difference between php-fpm and swoole

Difference: 1. "PHP-FPM" is only applicable to HTTPServer, while swoole is not only used for HTTPServer, but can also establish TCP connections; 2. "PHP-FPM" monitors Nginx transmission requests through the FastCGI protocol, while swoole Monitor event changes through Reactor.

The operating environment of this tutorial: windows10 system, PHP7.1 version, DELL G3 computer

What is the difference between php-fpm and swoole

1.PHP-FPM

Early versions of PHP did not have a built-in WEB server, but provided SAPI (Server API) to third parties Do docking. The very popular php-fpm now handles the communication between PHP and third-party WEB servers through the FastCGI protocol.

For example, the combination of Nginx php-fpm, fpm running in this way is Master/Worker mode, starting a Master process to monitor requests from Nginx, and then fork multiple Worker processes to handle the requests. Each Worker process can only handle one request. The life cycle of a single process is roughly as follows:

1. Initialization module.

2. Initialization request. The request here means requesting PHP to execute the code, not an HTTP request.

3. Execute PHP script.

4. End the request.

5. Close the module.

Swoole also uses the Master/Worker mode. The difference is that the Master process has multiple Reactor threads. The Master is just an event generator, responsible for monitoring the event changes of the Socket handle. Worker runs in a multi-process manner, receives requests from Reactor threads, and executes callback functions (written in PHP). The process of starting the Master process is roughly:

1. Initialize the module.

2. Initialization request. Because swoole needs to be run through cli, the global variables of PHP, such as $_SERVER, $_POST, $_GET, etc., will not be initialized when the request is initialized.

3. Execute PHP script. Including lexical and syntactic analysis, initialization of variables, functions, classes, etc., Master enters the listening state and will not end the process.

The principle of Swoole acceleration

The Reactor (epoll's IO reuse method) is responsible for monitoring the event changes of the Socket handle to solve high concurrency problems.

Save PHP code initialization time through memory resident. When using bulky frameworks, the acceleration effect of using swoole is very obvious.

2. Compare the differences

PHP-FPM

Master main process / Worker multi-process model.

Start Master and monitor requests transmitted from Nginx through FastCGI protocol.

Each Worker process corresponds to only one connection, which is used to execute complete PHP code.

After the PHP code is executed, all the memory occupied will be destroyed, and the next request needs to be re-initialized and other tedious operations.

Only used for HTTP Server.

Swoole

Master main process (composed of multiple Reactor threads)/Worker multi-process (or multi-thread) mode

Start Master and initialize PHP code, Reactor monitors event changes of Socket handle.

The main thread of Reactor is responsible for the balancing of multi-threads, and the Manager process manages multiple Worker processes, including TaskWorker processes.

Each Worker accepts requests from Reactor and only needs to execute the PHP code in the callback function part.

The PHP initialization code is only executed once when the Master starts. The Master enters the listening state and does not end the process.

It can not only be used for HTTP Server, but also can establish TCP connection and WebSocket connection.

Recommended learning: "PHP Video Tutorial"

The above is the detailed content of What is the difference between php-fpm and swoole. For more information, please follow other related articles on the PHP Chinese website!