Home  >  Article  >  Backend Development  >  Take a quick look! Non-authoritative test of mainstream PHP framework performance

Take a quick look! Non-authoritative test of mainstream PHP framework performance

藏色散人
藏色散人forward
2020-07-29 13:20:453004browse

Non-authoritative test of mainstream PHP framework performance

As a PHP developer and a technical developer of a start-up team, choosing a development framework is a very difficult thing.

If you use ThinkPHP, you can get started by recruiting a developer who has just graduated from a training institution, but decoupling performance and post-code is a headache. However, many third-party functions do not need to be written by yourself, as many experts have already paved the way.

If you use Laravel, it is said that it is very comfortable to write and has sufficient scalability, but the learning cost is a bit high. You can’t give junior developers half a month to learn the framework. And it is said that people in the world have revealed that the performance of Laravel is not very good, and the documentation is not particularly rich.

If you use Yii, the syntax is a bit cumbersome, and the separation of front-end and back-end code is a little troublesome, but the performance is very good, and it is already used by many large domestic companies. If an accident occurs, you can quickly Find Daniel to answer your questions.

It’s better to do a simple performance evaluation. You can’t go wrong by choosing one with excellent performance

Performance test

  • Testing time: May 2016 06th

  • Test tool: siege (Because ab of MAC system always appears pr_socket_recv: Connection reset by peer ( 54) error, so I chose siege)

  • Test machine: MacPro Core i5 processor/8GB memory/256GB SSD flash memory

  • Test environment: Apache PHP5.6

  • Framework version: ThinkPHP 3.2.3 Laravel 5.2 Yii2.0.5

  • Testing principle: Each test cycle is 5 times, taking medium data

Supplementary instructions: All projects are Let's start the test in the subdirectory

Result Description

Transactions:                2119 hits  处理请求总数量
Availability:               96.85 %  可用性
Elapsed time:                9.74 secs  运行时间
Data transferred:            1.31 MB 数据传输量
Response time:                0.60 secs 响应时间
Transaction rate:          217.56 trans/sec 每秒处理效率
Throughput:                0.13 MB/sec 每秒处理数据
Concurrency:              130.28 并发
Successful transactions:        2162 成功的请求
Failed transactions:              69 失败的请求
Longest transaction:            2.85 最长的单个请求
Shortest transaction:            0.01 最短的单个请求

Add a controller and enter HelloWorld 10,000 times in the controller

Concurrency 50 loops 10 times:

The first thing that came to us was ThinkPHP, which looked okay

Transactions:                 500 hits
Availability:              100.00 %
Elapsed time:                2.81 secs
Data transferred:           52.45 MB
Response time:                0.26 secs
Transaction rate:          177.94 trans/sec
Throughput:               18.67 MB/sec
Concurrency:               47.10
Successful transactions:         500
Failed transactions:               0
Longest transaction:            0.48
Shortest transaction:            0.03

Then came Laravle, well, a little disappointed

Transactions:                 500 hits
Availability:              100.00 %
Elapsed time:               13.33 secs
Data transferred:           52.45 MB
Response time:                1.27 secs
Transaction rate:           37.51 trans/sec
Throughput:                3.93 MB/sec
Concurrency:               47.55
Successful transactions:         500
Failed transactions:               0
Longest transaction:            3.64
Shortest transaction:            0.07

In the end, Yii

Transactions:                 500 hits
Availability:              100.00 %
Elapsed time:                4.84 secs
Data transferred:           52.45 MB
Response time:                0.46 secs
Transaction rate:          103.31 trans/sec
Throughput:               10.84 MB/sec
Concurrency:               47.65
Successful transactions:         500
Failed transactions:               0
Longest transaction:            0.88
Shortest transaction:            0.04

, which was more optimistic before the game, was concurrently 200 and looped 10 times:

First was ThinkPHP

Transactions:                1977 hits
Availability:               98.85 %
Elapsed time:               10.03 secs
Data transferred:          207.40 MB
Response time:                0.95 secs
Transaction rate:          197.11 trans/sec
Throughput:               20.68 MB/sec
Concurrency:              187.68
Successful transactions:        1977
Failed transactions:              23
Longest transaction:            1.22
Shortest transaction:            0.02

Then was Laravel

Transactions:                1890 hits
Availability:               94.50 %
Elapsed time:               51.85 secs
Data transferred:          198.27 MB
Response time:                4.88 secs
Transaction rate:           36.45 trans/sec
Throughput:                3.82 MB/sec
Concurrency:              178.00
Successful transactions:        1890
Failed transactions:             110
Longest transaction:           26.01
Shortest transaction:            0.07

Finally It's Yii

Transactions:                1996 hits
Availability:               99.80 %
Elapsed time:               18.95 secs
Data transferred:          209.39 MB
Response time:                1.79 secs
Transaction rate:          105.33 trans/sec
Throughput:               11.05 MB/sec
Concurrency:              188.57
Successful transactions:        1996
Failed transactions:               4
Longest transaction:            3.29
Shortest transaction:            0.10

I didn't expect that without optimization, ThinkPHP was the fastest, Yii was slightly faster, and Laravel finished the test falteringly. The results are somewhat unexpected, but the above test only represents the development environment. The framework will be optimized below to simulate the online environment.

Optimization Framework

ThinkPHP:

APP_DEBUG改为false

Laravel:

APP_DEBUG改为false
php artisan route:cache
php artisan optimize
php artisan config:cache
composer dumpautoload -o

Yii:

YII_DEBUG改为false
composer dumpautoload -o

Concurrency 200 loops 10 times:

ThinkPHP

Transactions:                1655 hits
Availability:               82.75 %
Elapsed time:                8.21 secs
Data transferred:          173.62 MB
Response time:                0.69 secs
Transaction rate:          201.58 trans/sec
Throughput:               21.15 MB/sec
Concurrency:              139.29
Successful transactions:        1655
Failed transactions:             345
Longest transaction:            7.83
Shortest transaction:            0.00

Laravel:

Transactions:                1520 hits
Availability:               76.00 %
Elapsed time:               34.95 secs
Data transferred:          159.45 MB
Response time:                3.15 secs
Transaction rate:           43.49 trans/sec
Throughput:                4.56 MB/sec
Concurrency:              136.84
Successful transactions:        1520
Failed transactions:             480
Longest transaction:           19.18
Shortest transaction:            0.00

Yii:

Transactions:                1704 hits
Availability:               85.20 %
Elapsed time:               15.16 secs
Data transferred:          178.76 MB
Response time:                1.46 secs
Transaction rate:          112.40 trans/sec
Throughput:               11.79 MB/sec
Concurrency:              164.21
Successful transactions:        1704
Failed transactions:             296
Longest transaction:            9.04
Shortest transaction:            0.00

The strange thing is that when the framework turns off the debugging mode, there are more failures. However, it is obvious that after simple optimization, Laravel's performance has been greatly improved, but it is still lower than the other two frameworks.

Conclusion

During the test, I felt depressed. I felt that my world view had collapsed, to the point of collapse.

  • ThinkPHP’s performance is twice as high as Yii and nearly four times higher than Laravel

  • Yii’s performance is relatively mediocre, but in the test Zhonghui clearly found that there were fewer request failures than the other two frameworks

  • Laravel is still elegant, but its performance is worrying. It is better to describe it in the words of netizens Those who learn will use it The person who dies

Finally

My project was developed using a self-built framework. Thanks to the power of composer, the development process went very smoothly. In the end Attached is the data of 200 concurrency and 10 cycles of our own framework. The framework is open source but very busy with updates. You are welcome to search PPPHP on github and build the framework with me.

Transactions:                1672 hits
Availability:               83.60 %
Elapsed time:                6.18 secs
Data transferred:          175.40 MB
Response time:                0.57 secs
Transaction rate:          270.55 trans/sec
Throughput:               28.38 MB/sec
Concurrency:              153.16
Successful transactions:        1672
Failed transactions:             328
Longest transaction:            4.57
Shortest transaction:            0.01

The above is the detailed content of Take a quick look! Non-authoritative test of mainstream PHP framework performance. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:segmentfault.com. If there is any infringement, please contact admin@php.cn delete