Why use swoole in php?

I have been studying Swoole in the past two months, so with the help of this article, I hope to bring Swoole to more people. Although Swoole may currently be positioned as a toy for some advanced phpers, which is intimidating to intermediate and low-level users, and may also be confused by some application scenarios, it is actually not that difficult.

The self-introduction on Swoole's official website is "PHP asynchronous network communication engine for production environments". First of all, Swoole is a network application development tool that supports Http, TCP, UDP, and WebSocket.

There are differences between Swoole and our traditional PHP development, and there are also concepts that need to be understood. If you use some current Swoole-based frameworks to develop, the development habits are similar to the traditional TP and LV frameworks.

So why use Swoole?

I think there are the following points:

Resident in memory, avoid performance losses caused by repeated loading, improve massive performance

Coroutine asynchronous, improve Concurrent processing capabilities for I/O-intensive scenarios (such as WeChat development, payment, login, etc.)

Conveniently develop Http, WebSocket, TCP, UDP and other applications, and can communicate with hardware

PHP High-performance microservice architecture has become a reality

Resident memory

Currently, the traditional PHP framework has to load the framework file and configure it before processing each request. operate. This may have become a big cause of performance issues, but with Swoole there is no such problem, once loaded and used many times.

Coroutine

As shown in the figure below, this is a scenario where the same thread handles concurrent requests. For example, one of your interfaces needs to call other api interfaces or read and write For large files, the advantages of traditional synchronous blocking and coroutine asynchronous are reflected.

Detailed explanation of why Swoole coroutines are suitable for I/O-intensive scenarios

When it comes to coroutines, we must first briefly talk about processes and threads. As we all know, processes It takes up a lot of resources, and creating a large number of processes in order to handle requests is definitely not worth the gain. There are many multi-threaded applications. At the CPU level, several cores will perform several tasks. Once too many threads are created, there will be a loss in thread scheduling.

Coroutines are implemented on a single-thread basis, which can maximize the use of CPU resources without wasting them while waiting for I/O. Of course, the more coroutines, the more memory they occupy, but this is acceptable. Compared with processes and threads, the resources occupied are relatively small.

When using coroutines, when encountering scenarios such as reading and writing files, requesting interfaces, etc., the coroutines will be automatically suspended and the CPU will be given to other coroutines to perform tasks. This can improve single-threaded CPU resource utilization. Reduce waste, thereby improving performance.

Coroutine code example:

<?php
use Swoole\Coroutine as co;
 
// 协程
$time = microtime(true);
// 创建10个协程
for($i = 0; $i < 10; ++$i)
{
    // 创建协程
    go(function() use($i){
        co::sleep(1.0); // 模拟请求接口、读写文件等I/O
        echo $i, PHP_EOL;
    });
}
swoole_event_wait();
echo &#39;co time:&#39;, microtime(true) - $time, &#39; s&#39;, PHP_EOL;
 
// 同步
$time = microtime(true);
// 创建10个协程
for($i = 0; $i < 10; ++$i)
{
    sleep(1); // 模拟请求接口、读写文件等I/O
    echo $i, PHP_EOL;
}
echo &#39;sync time:&#39;, microtime(true) - $time, &#39; s&#39;, PHP_EOL;

Running results:

0
9
8
7
6
5
4
3
2
1
co time:1.0087130069733 s
0
1
2
3
4
5
6
7
8
9
sync time:10.010055065155 s

As can be seen from the above results, coroutine execution is not sequential, and the performance is higher. In sleep The task execution rights of the current thread will be handed over to other coroutines.

Create Http service

In fact, it is not as difficult as imagined. Look at the code:

$http = new swoole_http_server("127.0.0.1", 9501);
$http->on('request', function ($request, $response) {
    $response->end("<h1>Hello Swoole. #".rand(1000, 9999)."</h1>");
});
$http->start();

Microservice

Tars is the unified application framework TAF (Total Application Framework) of the backend logic layer that Tencent has been using from 2008 to today. It currently supports C, Java, PHP, and Nodejs languages. This framework provides users with a complete set of solutions involving development, operation and maintenance, and testing, helping a product or service to quickly develop, deploy, test, and go online. It integrates scalable protocol encoding and decoding, high-performance RPC communication framework, name routing and discovery, release monitoring, log statistics, configuration management, etc. Through it, you can quickly build your own stable and reliable distributed applications using microservices, and Achieve complete and effective service governance.

If there are any mistakes, please point them out. I really want to recommend Swoole to everyone!

The above is the detailed content of Why use swoole in php?. For more information, please follow other related articles on the PHP Chinese website!