How to make your Laravel return a 'hello world!' in 15 milliseconds

                                                       

The following tutorial column from laravel will introduce to you how to make your Laravel return a "hello world!" within 15 milliseconds. I hope it will be helpful to friends who need it. help!

First of all, I think that returning the most basic Hello world! string is the most basic request process among all projects based on Laravel. In addition, any http request in the project will carry more time-consuming operations such as business logic and database queries, and the execution time of these logics is uncontrollable and non-comparable. In other words, any other request will not take less time than returning a Hello world! string. Therefore, by comparing the most basic Hello world request response time, we can see the impact of different optimizations on the Laravel framework from startup to end of execution.

Recommended: The latest five Laravel video tutorials

Test parameters

Parameters	Version
Server	1c processor, 1G memory, 1M bandwidth
PHP Version	8.0
Process Management	PHP-FPM

Default configuration response time

It can be seen that after installing PHP, under the default configuration, a Hello world!On average it takes about 140ms. Next, let’s get started!

Round 1: Laravel cache

Laravel provides us with a very convenient artisan command to enable the cache function. Effectively reduces the number of How to make your Laravel return a hello world! in 15 milliseconds reads. The php artisan optimize command includes the php artisan config:cache and php artisan route:cache commands, but one more Files will appear. cache. Execute the following 5 commands in sequence:

root@Aliyun-ECS / # php artisan optimize
root@Aliyun-ECS / # php artisan config:cache
root@Aliyun-ECS / # php artisan event:cache
root@Aliyun-ECS / # php artisan route:cache
root@Aliyun-ECS / # php artisan view:cache

Let’s take a look at the response time:

It can be seen that Laravel’s cache is Basic request, no noticeable impact.

Round 2: Turn on opcache

This time, I decided to use the method with the most obvious speed-up effect: Turn on opcacheExtension. Since I installed php8 using the remi source, it will be easier for me to install the opcache extension here. For installation of other versions, please Google it yourself.

root@Aliyun-ECS / # yum install php80-php-opcache

After waiting for the installation to complete, we restart php, and then check whether the extension has been installed:

root@Aliyun-ECS / # systemctl restart php80-php-fpm
root@Aliyun-ECS / # php -i|grep opcache.enable
opcache.enable => On => On
opcache.enable_cli => On => On
opcache.enable_How to make your Laravel return a hello world! in 15 milliseconds_override => Off => Off

ok, the opcache extension has been enabled Okay, let’s take a look at the response time of Hello world!:

##OHHHHHH! The effect is so obvious that it suddenly drops to within

30ms, which improves the response time by nearly 5 times. Note that the first request will be slower because opcache is writing the cache. After one access, the speed will skyrocket. Are you satisfied here? Look at the title of the article, we need to further increase our efforts!

Round 3: Turn on swoole

swoole Everyone knows that the module loads the application into memory in advance so that when processing the request , reducing the How to make your Laravel return a hello world! in 15 milliseconds reading and loading process, giving PHP wings. Install the swoole extension below, please Google for other versions.

root@Aliyun-ECS / # yum install php80-php-pecl-swoole

As usual, after installation, check whether the installation is successful:

root@Aliyun-ECS / # systemctl restart php80-php-fpm
root@Aliyun-ECS / # php -i|grep swoole.enable
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off

The extension has been enabled, but it cannot be tested yet. Because

swoole is an extension in cli mode, php-fpm cannot be used. So we need to implement a http application in cli mode. But in fact, we don’t need to manually write the http application ourselves. There are big guys in the community who have already written it. As the saying goes, "Forefathers plant trees, and future generations enjoy the shade." We introduce the laravel-swoole software package and start a http service. It's very simple.

// 引入软件包
root@Aliyun-ECS / # composer require swooletw/laravel-swoole
// 发布配置文件
root@Aliyun-ECS / # php artisan vendor:publish --tag=laravel-swoole

After performing the above two steps, you can find the two configuration How to make your Laravel return a hello world! in 15 millisecondss

swoole_http and swoole_websocket in the config directory of the project. A basic Hello world! test, no need to modify the default configuration, we only add SWOOLE_HTTP_HOST=0.0.0.0 and ## in the .env How to make your Laravel return a hello world! in 15 milliseconds of the project #SWOOLE_HTTP_PORT=2020, which means to start a http listening program on the 2020 port. 0.0.0.0 means any IP can be accessed remotely. <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class="brush:php;toolbar:false">// .env SWOOLE_HTTP_HOST=0.0.0.0 SWOOLE_HTTP_PORT=2020</pre><div class="contentsignin">Copy after login</div></div> The basic configuration modification is completed, we start the

http

application of laravel-swoole: <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class="brush:php;toolbar:false">root@Aliyun-ECS / # php artisan swoole:http start Starting swoole http server...Swoole http server started: &lt;http:&gt;&lt;/http:&gt;</pre><div class="contentsignin">Copy after login</div></div>At this time we visit

2020

Port, you can test the application expanded using swoole. Let’s look at the response time of the request:

Good guy! Directly do it within

15ms

. The first time here takes a long time because opcache is turned on and the cache will be written. But the opcache write cache here is much faster than the one in Round 2 that only opens the opache extension. This is all the result of swoole . <h1> <span class="header-link octicon octicon-link"></span>Conclusion</h1> <p>I tested it again, only enabling the <code>swoole extension without enabling the opcache, and found that the response time was the same as two The response time is the same for both extensions enabled. In other words, after having swoole, opcache will be useless? I have to ask the big guys for advice on this. Here is a simple comparison:

Through practical comparison, it is found that enabling the opcache and swoole extensions at the same time has the fastest response time. Fast.

Other questions

• PHP-FPM process management, why is the master process created? Unscientific

Thanks

Thanks @Hesunfly for the answer. Sometimes the extended information viewed using the php -i mode on the command line is inconsistent with the extended information viewed using phpinfo() on the page. Here is a quote from @Hesunfly's original words:
"Some distributions do share the configurations of cli and fpm, such as for mac The php installed by brew only has one php.ini. But when I install it under centos and ubuntu, I usually distinguish between cli and fpm."

The above is the detailed content of How to make your Laravel return a 'hello world!' in 15 milliseconds. For more information, please follow other related articles on the PHP Chinese website!