Swoole provides a complete process management mechanism. When the Worker process exits abnormally, such as a fatal error in PHP, being accidentally killed by other programs, or exiting normally after reaching the max_request number. (Recommended learning: swoole video tutorial )
The main process will restart the new Worker process. Code can be written in the Worker process like ordinary apache php or php-fpm. There is no need to write asynchronous callback code like Node.js.
Worker process
Accepts the request packet delivered by the Reactor thread, and executes the PHP callback function to process the data
Generates response data and sends it to the Reactor thread , sent to the TCP client by the Reactor thread
It can be in asynchronous non-blocking mode or synchronous blocking mode
Worker runs in a multi-process manner
worker_num
Description: Specify the number of worker processes to start.
Note: swoole is the master-> n * worker mode. The more worker processes are opened, the greater the server load capacity, but the corresponding server will occupy more memory. At the same time, when there are too many worker processes, the system overhead caused by switching between processes will be greater. Therefore, it is recommended that the number of worker processes opened is 1-4 times the number of CPU cores.
Example:
'worker_num' => 8
The above is the detailed content of How to call swoole's worker. For more information, please follow other related articles on the PHP Chinese website!