发表新帖

基于swoole提升laravel API接口10-50倍的性能

大家好， 这是我在接口服务化时的一个尝试， 利用swoole并实现fastcgi协议， 常驻内存并替代php-fpm, 可以大大减少laravel框架带来的性能损耗， 又能享受laravel框架的优雅代码。

缺点是目前仅适合无状态的接口调用场景。

我特意写了一个例子： github.com/chefxu/stone-laravel-example (不能发外链)

性能对比结果如下 7600QPS VS 120QPS：

{{{
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>

Benchmarking 192.168.1.10 (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests

Server Software:        nginx
Server Hostname:        192.168.1.10
Server Port:            7412

Document Path:          /workbench/listdata
Document Length:        211 bytes

Concurrency Level:      30
Time taken for tests:   8.335 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      1185252 bytes
HTML transferred:       211000 bytes
Requests per second:    119.97 [#/sec] (mean)
Time per request:       250.054 [ms] (mean)
Time per request:       8.335 [ms] (mean, across all concurrent requests)
Transfer rate:          138.87 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:   100  246  64.9    251     763
Waiting:      100  246  64.9    251     763
Total:        101  247  64.8    251     763

Percentage of the requests served within a certain time (ms)
  50%    251
  66%    263
  75%    271
  80%    276
  90%    299
  95%    336
  98%    425
  99%    531
 100%    763 (longest request)
}}}

{{{
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>

Benchmarking 192.168.1.10 (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:        stone
Server Hostname:        192.168.1.10
Server Port:            7412

Document Path:          /server/workbench/listdata
Document Length:        211 bytes

Concurrency Level:      100
Time taken for tests:   1.305 seconds
Complete requests:      10000
Failed requests:        0
Total transferred:      3400000 bytes
HTML transferred:       2110000 bytes
Requests per second:    7662.11 [#/sec] (mean)
Time per request:       13.051 [ms] (mean)
Time per request:       0.131 [ms] (mean, across all concurrent requests)
Transfer rate:          2544.06 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.2      0       3
Processing:     5   13   1.8     13      25
Waiting:        5   13   1.8     13      25
Total:          7   13   1.8     13      25

Percentage of the requests served within a certain time (ms)
  50%     13
  66%     13
  75%     14
  80%     14
  90%     15
  95%     16
  98%     17
  99%     20
 100%     25 (longest request)
}}}

愿swoole越来越好！

发布于9年前 · 7 次浏览 · 来自提问

crazy runner

缺点是目前仅适合无状态的接口调用场景。

我特意写了一个例子： github.com/chefxu/stone-laravel-example (不能发外链)

性能对比结果如下 7600QPS VS 120QPS：

{{{
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>

Server Software:        nginx
Server Hostname:        192.168.1.10
Server Port:            7412

Document Path:          /workbench/listdata
Document Length:        211 bytes

Percentage of the requests served within a certain time (ms)
  50%    251
  66%    263
  75%    271
  80%    276
  90%    299
  95%    336
  98%    425
  99%    531
 100%    763 (longest request)
}}}

{{{
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>

Server Software:        stone
Server Hostname:        192.168.1.10
Server Port:            7412

Document Path:          /server/workbench/listdata
Document Length:        211 bytes

Percentage of the requests served within a certain time (ms)
  50%     13
  66%     13
  75%     14
  80%     14
  90%     15
  95%     16
  98%     17
  99%     20
 100%     25 (longest request)
}}}

愿swoole越来越好！

登录后参与评论

2017-08-08

wish

2017-08-11

原

原来微博的名字竟然可以有这么长

2019-05-29

play_soso