在现代化 PHP 高级开发中，Swoole 为 PHP 带来了更多可能，如：常驻内存、协程，关于传统的 Apache/FPM 模式与常驻内存模式(同步)的巨大差异，之前我做过测试，大家能直观的感受到性能的巨大提升，但是协程到来后，又带来了多少性能的提升呢？提升的又是哪方面的性能？下面逐步测试一下。

传统的 Apache/FPM 模式与常驻内存模式(同步)的测试文章：
MixPHP 并发性能全面对比测试

协程的优势

协程模式与常驻内存模式(同步)/传统模式相比：

常驻模式/传统模式都属于同步阻塞编程，由于同一个进程不能并行处理请求，所以为了提高并发，只能开启更多的进程，通常超过 100 甚至更多，每个进程都有基础的内存消耗，加起来就很多了，而且受限于 Linux 总进程数限制，并发总数无法突破，加上进程非常多之后，CPU 需要更多的线程切换，浪费了很多性能，当然相比 FPM 的传统模式每次都需从头开始，常驻模式还是要好非常多的，但是协程显然更加优秀。

协程模式的执行方式：

协程模式中一个进程可以同时执行 N 个请求，但同一时刻只执行其中的某一个请求，也就是说，当执行到 MySQL/Redis 这些客户端时，由于需要等待客户端响应，常驻模式/传统模式通常是在傻傻的等待响应，而协程这个时候会挂起当前协程，切换到其他协程中去处理其他请求，所以协程能同时处理 N 个请求，每增加一个请求只需增加一些内存消耗，相比增加一个进程的内存消耗，显然是少太多的，由于协程能并行处理，所以通常只需配置于 CPU 数量 1～2 倍左右的进程数即可，更少的进程带来更少的 CPU 线程切换，又减少很多性能损耗。

开始测试

MixPHP 是一个基于 Swoole 的FPM、常驻内存、协程三模 PHP 高性能框架，由于该框架同时具备常驻内存模式、协程模式，所以能很方便的测试结果。

测试环境：

docker 容器，限制只能使用 1 CPU。

其他参数如下：

```Server Name: mix-httpd
Framework Version: 1.1.0-RC
PHP Version: 7.2.9
Swoole Version: 4.1.0
Listen Addr: 127.0.0.1
Listen Port: 9501
```

代码：

模拟常用的 HTTP 开发需求，执行三个 SQL 请求。



// 默认动作

public function actionIndex()

{

    PDO::createCommand("select * from `test` where id = 1")->queryOne();

    PDO::createCommand("select * from `test` where id = 2")->queryOne();

    return PDO::createCommand("select * from `test` limit 5")->queryAll();

}

测试结果

常驻内存模式(同步)：

进程数 并发数 RPS
8 100 838.65
8 300 683.78
8 500 688.56
50 100 770.69
50 300 304.90
50 300 378.95

协程模式：

进程数 并发数 RPS
8 100 834.12
8 300 837.50
8 500 824.14

协程在本次测试中并没有像之前的传统 Apache/FPM 模式与常驻内存模式(同步)的测试一样展现出巨大的性能提升，说明：

  • 在少量能快速响应的 SQL 请求中，协程的提升并不明显，应该要在响应时间更大时，才能感受到协程优势。
  • 常驻内存模式的进程数配置过多，并发性能反而会降低，该问题同样适用于传统 Apache/FPM 模式。

常驻内存模式(同步)详细测试

首先 8 个 Worker 进程，并发 100 测试，RPS 为 838.65。



C:\Users\EDZ>ab -n 10000 -c 100 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      100

Time taken for tests:   11.924 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    838.65 [#/sec] (mean)

Time per request:       119.239 [ms] (mean)

Time per request:       1.192 [ms] (mean, across all concurrent requests)

Transfer rate:          217.85 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    0   0.2      0       4

Processing:    20  118  18.3    118     195

Waiting:       19  118  18.4    118     195

Total:         20  118  18.4    119     195

Percentage of the requests served within a certain time (ms)

  50%    119

  66%    126

  75%    130

  80%    133

  90%    141

  95%    147

  98%    155

  99%    161

 100%    195 (longest request)

然后使用 8 个 Worker 进程，并发 300 测试，RPS 为 683.78。



C:\Users\EDZ>ab -n 10000 -c 300 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      300

Time taken for tests:   14.624 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    683.78 [#/sec] (mean)

Time per request:       438.735 [ms] (mean)

Time per request:       1.462 [ms] (mean, across all concurrent requests)

Transfer rate:          177.62 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    0  30.0      0    3000

Processing:    62  432 493.4    354    3457

Waiting:       54  431 488.1    354    3455

Total:         62  433 494.1    354    3457

Percentage of the requests served within a certain time (ms)

  50%    354

  66%    373

  75%    385

  80%    392

  90%    411

  95%    432

  98%   3170

  99%   3266

 100%   3457 (longest request)

然后使用 8 个 Worker 进程，并发 500 测试，RPS 为 688.56。



C:\Users\EDZ>ab -n 10000 -c 500 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      500

Time taken for tests:   14.523 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    688.56 [#/sec] (mean)

Time per request:       726.150 [ms] (mean)

Time per request:       1.452 [ms] (mean, across all concurrent requests)

Transfer rate:          178.87 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    0  30.0      0    3000

Processing:   102  707 618.4    596    3632

Waiting:       89  703 605.6    595    3629

Total:        102  707 618.9    596    3633

Percentage of the requests served within a certain time (ms)

  50%    596

  66%    620

  75%    635

  80%    645

  90%    679

  95%   3125

  98%   3401

  99%   3495

 100%   3633 (longest request)

现在调整为 50 进程，100 并发测试，RPS 为 770.69。
进程的增加并没有带来并发量的提升。



C:\Users\EDZ>ab -n 10000 -c 100 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      100

Time taken for tests:   12.975 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    770.69 [#/sec] (mean)

Time per request:       129.754 [ms] (mean)

Time per request:       1.298 [ms] (mean, across all concurrent requests)

Transfer rate:          200.20 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    1  42.4      0    3000

Processing:    10  128 499.8     56    7137

Waiting:       10  127 495.8     55    7137

Total:         11  129 503.3     56    7137

Percentage of the requests served within a certain time (ms)

  50%     56

  66%     72

  75%     86

  80%     97

  90%    133

  95%    179

  98%    312

  99%   3052

 100%   7137 (longest request)

50 进程，300 并发测试，RPS 为 304.90。
对比 8 个进程时的结果，并发量降低非常明显，看来进程数过多并不能提升性能，反而会降低性能。



C:\Users\EDZ>ab -n 10000 -c 300 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      300

Time taken for tests:   32.798 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    304.90 [#/sec] (mean)

Time per request:       983.942 [ms] (mean)

Time per request:       3.280 [ms] (mean, across all concurrent requests)

Transfer rate:          79.20 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    3  90.0      0    3001

Processing:    25  976 1339.8    189    3694

Waiting:       23  954 1316.5    188    3691

Total:         25  979 1341.0    189    3694

Percentage of the requests served within a certain time (ms)

  50%    189

  66%    289

  75%   3094

  80%   3113

  90%   3184

  95%   3249

  98%   3315

  99%   3375

 100%   3694 (longest request)

50 进程，500 并发测试，RPS 为 378.95。



C:\Users\EDZ>ab -n 10000 -c 500 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      500

Time taken for tests:   26.389 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    378.95 [#/sec] (mean)

Time per request:       1319.431 [ms] (mean)

Time per request:       2.639 [ms] (mean, across all concurrent requests)

Transfer rate:          98.44 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    2  79.4      0    3001

Processing:    64 1306 1434.7    341    3962

Waiting:       17 1224 1391.4    321    3959

Total:         65 1308 1435.2    342    3963

Percentage of the requests served within a certain time (ms)

  50%    342

  66%   3142

  75%   3168

  80%   3195

  90%   3292

  95%   3374

  98%   3467

  99%   3516

 100%   3963 (longest request)

协程模式详细测试

首先 8 个 Worker 进程，并发 100 测试，RPS 为 834.12。



C:\Users\EDZ>ab -n 10000 -c 100 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      100

Time taken for tests:   11.989 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    834.12 [#/sec] (mean)

Time per request:       119.886 [ms] (mean)

Time per request:       1.199 [ms] (mean, across all concurrent requests)

Transfer rate:          216.68 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    0   0.3      0       4

Processing:    84  119   9.8    122     165

Waiting:       84  119   9.8    122     164

Total:         84  119   9.8    123     165

Percentage of the requests served within a certain time (ms)

  50%    123

  66%    124

  75%    125

  80%    125

  90%    126

  95%    128

  98%    131

  99%    137

 100%    165 (longest request)

然后使用 8 个 Worker 进程，并发 300 测试，RPS 为 837.50。



C:\Users\EDZ>ab -n 10000 -c 300 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      300

Time taken for tests:   11.940 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    837.50 [#/sec] (mean)

Time per request:       358.207 [ms] (mean)

Time per request:       1.194 [ms] (mean, across all concurrent requests)

Transfer rate:          217.55 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    1  42.4      0    3001

Processing:    86  354 1043.0    161    7172

Waiting:       86  344 1011.9    160    7172

Total:         86  355 1044.5    161    7172

Percentage of the requests served within a certain time (ms)

  50%    161

  66%    182

  75%    199

  80%    212

  90%    251

  95%    302

  98%   6103

  99%   6135

 100%   7172 (longest request)

然后使用 8 个 Worker 进程，并发 500 测试，RPS 为 824.14。



C:\Users\EDZ>ab -n 10000 -c 500 http://www.a.com/

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>

Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/

Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.a.com (be patient)

Completed 1000 requests

Completed 2000 requests

Completed 3000 requests

Completed 4000 requests

Completed 5000 requests

Completed 6000 requests

Completed 7000 requests

Completed 8000 requests

Completed 9000 requests

Completed 10000 requests

Finished 10000 requests

Server Software:        nginx/1.13.9

Server Hostname:        www.a.com

Server Port:            80

Document Path:          /

Document Length:        101 bytes

Concurrency Level:      500

Time taken for tests:   12.134 seconds

Complete requests:      10000

Failed requests:        0

Total transferred:      2660000 bytes

HTML transferred:       1010000 bytes

Requests per second:    824.14 [#/sec] (mean)

Time per request:       606.690 [ms] (mean)

Time per request:       1.213 [ms] (mean, across all concurrent requests)

Transfer rate:          214.08 [Kbytes/sec] received

Connection Times (ms)

              min  mean[+/-sd] median   max

Connect:        0    0   0.3      0       4

Processing:    92  332 585.3    198    6931

Waiting:       91  331 585.5    196    6931

Total:         92  332 585.3    198    6931

Percentage of the requests served within a certain time (ms)

  50%    198

  66%    242

  75%    284

  80%    334

  90%    587

  95%    932

  98%   1216

  99%   2390

 100%   6931 (longest request)

MixPHP

GitHub: https://github.com/mixstart/m...
官网：http://www.mixphp.cn/

原文地址：https://segmentfault.com/a/1190000016383096

Swoole 同步模式与协程模式的对比的更多相关文章

  1. python进阶：Python进程、线程、队列、生产者/消费者模式、协程

    一.进程和线程的基本理解 1.进程 程序是由指令和数据组成的,编译为二进制格式后在硬盘存储,程序启动的过程是将二进制数据加载进内存,这个启动了的程序就称作进程(可简单理解为进行中的程序).例如打开一个 ...

  2. swoole深入学习 8. 协程 转

    版权声明:本文为博主原创文章,遵循CC 4.0 BY-SA版权协议,转载请附上原文出处链接和本声明. 本文链接:https://blog.csdn.net/yangyi2083334/article/ ...

  3. python3 - 多线程和协程速率测试对比

    多线程和协程都属于IO密集型,我通过以下用例测试多线程和协程的实际速率对比. 实例:通过socket客户端以多线程并发模式请求不同服务器端(这里服务器端分2种写法:第一种服务器通过协程实现,第二种服务 ...

  4. python3下multiprocessing、threading和gevent性能对比----暨进程池、线程池和协程池性能对比

    python3下multiprocessing.threading和gevent性能对比----暨进程池.线程池和协程池性能对比   标签: python3 / 线程池 / multiprocessi ...

  5. Coroutine(协程)模式与线程

    概念 协程(Coroutine)这个概念最早是Melvin Conway在1963年提出的,是并发运算中的概念,指两个子过程通过相互协作完成某个任务,用它可以实现协作式多任务,协程(coroutine ...

  6. Swoole 4.1.0 正式版发布，支持原生 Redis/PDO/MySQLi 协程化

    重大新特性 支持 Redis/PDO/MySQLi 从4.1.0版本开始支持了对PHP原生Redis.PDO.MySQLi协程化的支持. 可使用Swoole\Runtime::enableCorotu ...

  7. 协程与Swoole的原理，相关应用以及适用场景等

    什么是协程 协程(Coroutine)也叫用户态线程,其通过协作而不是抢占来进行切换.相对于进程或者线程,协程所有的操作都可以在用户态完成,创建和切换的消耗更低.协程是进程的补充,或者是互补关系. 要 ...

  8. {python之协程}一 引子 二 协程介绍 三 Greenlet 四 Gevent介绍 五 Gevent之同步与异步 六 Gevent之应用举例一 七 Gevent之应用举例二

    python之协程 阅读目录 一 引子 二 协程介绍 三 Greenlet 四 Gevent介绍 五 Gevent之同步与异步 六 Gevent之应用举例一 七 Gevent之应用举例二 一 引子 本 ...

  9. Zend 官方框架增加 Swoole 协程支持 ！

    前言 Zend Framework 是 PHP 的官方框架,随着 Zend-Expressive-Swoole 0.2.2 的发布,率先支持了 Swoole 4 的协程功能,现在可以仅通过一个配置即可 ...

随机推荐

  1. matlab7安装后的常见问题

    1.有时候.打开MatLab7时,会弹出"找不到指定的模块"对话框,如图(1)所看到的: 图(1) 找不到指定模块 产生这个问题的解决办法是.你的BLAS_VERSION环境变量没 ...

  2. iOS项目开发实战——使用Xcode6设计自己定义控件与图形

    在iOS开发中,有很多控件都是Xcode默认提供的.使用这些控件是很方便的.可是因为某些须要.须要自己设计控件,那么应该怎么做呢?在Xcode6中提供了这种接口,同意开发人员高速开发自己定义控件,而且 ...

  3. Unity3D与JSP TomCatserver传递数据和文件( 二 ) Unity3D向java传输表单

    扫码关注微信公众号,获取最新资源 经历了一天的工作.我又来更新啦...白天手欠,把上一个给删了.明天重写吧.. 废话不多说.我们先去Unity里创建一个能够输入username和password的登录 ...

  4. 安装visual studio 2013【转】

    本文转载自:http://blog.csdn.net/tina_ttl/article/details/51544733#1下载-visual-studio-ultimate-2013安装包 微软已经 ...

  5. git如何解决冲突（master分支的上的冲突--太岁头上动土）

    欢迎加入前端交流群交流知识&&获取视频资料:749539640 git是什么就不废话了,详情点击 出现以下情况怎么解决? 有个index.ts文件 export const ENV = ...

  6. Linux下清屏的方法

    转自“https://blog.csdn.net/lis_12/article/details/54943626” clear,刷新屏幕,本质上是让终端显示页向后翻了一页,如果向上滚动屏幕还可以看到之 ...

  7. 转载【梦想天空（山边小溪）】Web 开发人员和设计师必读文章推荐【系列二十九】

    博客地址:http://www.cnblogs.com/lhb25/p/must-read-links-for-web-designers-and-developers-volume-29.html

  8. C# WinForm DataGridView 给标题列增加序号及格式化某个字段

    DataGridView 给标题列增加序号 private void dataGridView1_DataBindingComplete(object sender, DataGridViewBind ...

  9. Django之缓存机制

    1.1 缓存介绍 1.缓存的简介 在动态网站中,用户所有的请求,服务器都会去数据库中进行相应的增,删,查,改,渲染模板,执行业务逻辑,最后生成用户看到的页面. 当一个网站的用户访问量很大的时候,每一次 ...

  10. guice基本使用,三种注入方式（二）

    guice提供了强大的注入方式. 1.属性注入 2.构造器注入 3.set方式注入 1.属性注入: package com.ming.user.test; import com.google.inje ...