PHP swoole 和 nodeJs性能分析
js出了个nodejs,我们技术老大前段时间发了个技术邮件说php支持多线程,异步,非阻塞 还打着旗号说要灭掉nodejs,官方网站上说swoole的性能已经最少也和nodejs可以媲美了,这个需要用数据说话,周末的时候有空就顺手测试了一下这两个东东!下面是测试报告哈。
首先我用127.0.0.1:8000端口测试swoole, 用127.0.0.1:1337测试nodejs
有图有真相:(稍后传,不会用mac把截图保存!汗!各位看客有谁会的教教我哈!编程都变傻了)
测试环境:(我这是来秀电脑配置的?哈哈哈!)
处理器:2.7GHz i7
内存:16GB 1600hz DDR3
系统 MAC OS X
测试过程:下图中可以看到我开启了swoole的debug模式,会有执行日志出现,因此实际生产环境可能swoole比测试的要高
测试结果:
1.PHPswoole的测试结果:
~mysql|? ab -n 5000 -c 100 http://127.0.0.1:8000/ This is ApacheBench, Version 2.3 <$Revision: 655654 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 127.0.0.1 (be patient) Completed 500 requests Completed 1000 requests Completed 1500 requests Completed 2000 requests Completed 2500 requests Completed 3000 requests Completed 3500 requests Completed 4000 requests Completed 4500 requests Completed 5000 requests Finished 5000 requests Server Software: Server Hostname: 127.0.0.1 Server Port: 8000 Document Path: / Document Length: 0 bytes Concurrency Level: 100 Time taken for tests: 1.411 seconds Complete requests: 5000 Failed requests: 0 Write errors: 0 Total transferred: 55330 bytes HTML transferred: 0 bytes Requests per second: 3543.00 [#/sec] (mean) Time per request: 28.225 [ms] (mean) Time per request: 0.282 [ms] (mean, across all concurrent requests) Transfer rate: 38.29 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 3 1.2 3 7 Processing: 17 25 16.7 23 143 Waiting: 1 9 12.9 7 136 Total: 20 28 16.6 26 143 Percentage of the requests served within a certain time (ms) 50% 26 66% 27 75% 27 80% 27 90% 28 95% 29 98% 141 99% 142 100% 143 (longest request)
2.nodejs的测试结果:
~mysql|? ab -n 5000 -c 100 http://127.0.0.1:1337/ This is ApacheBench, Version 2.3 <$Revision: 655654 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 127.0.0.1 (be patient) Completed 500 requests Completed 1000 requests Completed 1500 requests Completed 2000 requests Completed 2500 requests Completed 3000 requests Completed 3500 requests Completed 4000 requests Completed 4500 requests Completed 5000 requests Finished 5000 requests Server Software: Server Hostname: 127.0.0.1 Server Port: 1337 Document Path: / Document Length: 12 bytes Concurrency Level: 100 Time taken for tests: 1.215 seconds Complete requests: 5000 Failed requests: 0 Write errors: 0 Total transferred: 565000 bytes HTML transferred: 60000 bytes Requests per second: 4116.49 [#/sec] (mean) Time per request: 24.293 [ms] (mean) Time per request: 0.243 [ms] (mean, across all concurrent requests) Transfer rate: 454.26 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 0 0 0.6 0 5 Processing: 2 24 21.0 21 175 Waiting: 2 24 20.8 21 174 Total: 6 24 20.9 21 175 Percentage of the requests served within a certain time (ms) 50% 21 66% 22 75% 23 80% 24 90% 26 95% 32 98% 159 99% 170 100% 175 (longest request)
上面的ab测试中:每秒100的并发量共向接口请求5000次。
PHP和nodejs成绩都还不错,关键是Swoole的环境我用了--debug导致有很多命令会输出,暂时有不会改回去,(稍后在公司测试环境重新测试下)
Time taken for tests: 1.411 seconds共耗时
Requests per second: 3543.00 [#/sec] (mean)
nodeJS
Time taken for tests: 1.215 seconds共耗时
Requests per second: 4116.49 [#/sec] (mean)
从测试结果来看,虽然swoole的测试数据稍微逊色了一点,但是这并不影响我对swoole的看法(况且配置可能不是很好),我觉的对于一个C语言编写的PHP,这个已经比我们目前的环境要好的多了。
郑重声明:本站内容如果来自互联网及其他传播媒体,其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享,并不代表本站赞同其观点和对其真实性负责,也不构成任何其他建议。