2. 程式人生 > >Swoole 同步模式與協程模式的對比

Swoole 同步模式與協程模式的對比

阿新 • • 發佈：2018-11-16

在現代化 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 同步模式與協程模式的對比

在現代化 PHP 高階開發中，Swoole 為 PHP 帶來了更多可能，如：常駐記憶體、協程，關於傳統的 Apache/FPM 模式與常駐記憶體模式(同步)的巨大差異，之前我做過測試，大家能直觀的感受到效能的巨大提升，但是協程到來後，又帶來了多少效能的提升呢？提升的又是哪方面的效能？下面逐步測試一下。 傳統

單例模式與線程安全問題淺析

ati 多線程 con data 非常完美 賦值 return span author 近期看到到Struts1與Struts2的比較。說Struts1的控制器是單例的，線程不安全的；Struts2的多例的，不存在線程不安全的問題。之後又想到了之前自

32位程序下調用64位函數——進程32位模式與64位模式切換

always imu tab 之間 pointer icm bool list ack 之前學習的32位進程中調用64位進程函數的知識整理一下，也就是32位模式與64位模式之間的切換。 相關博客：http://www.cnblogs.com/lanrenxinxin/p/4

1、Spring單例模式與線程安全

局部變量 提醒 業務 bean 環境 protect 線程安全問題 for 最快 引自：https://www.cnblogs.com/wxd0108/p/5524756.html 一、問題背景 這段時間在做項目的時候，考慮到Spring中的bean默認是單例模式的，那麽當

ajax 同步模式與異步模式

scrip 布爾值 sync 區別 ole get () rip 布爾 <script> // console.time(‘abc‘) // for (var i = 0; i < 100000000; i++) {} // consol

線程、進程與協程2

部分 tin 另一個 locking 寄存器 out 可能 ket .so 一、協程 什麽是協程？ 協程，又名微線程，纖程，英文名為Coroutine。 協程是一種用戶態的輕量級線程。 協程擁有自己的寄存器上下文和棧。協程調度切換時，將寄存器上下文和棧保存到其他地方，在切回

線程及與進程的對比

減少 可見 博文 單位 多個 質量 分發 .com 之間 一、為什麽要引入線程 　　進程是為了提高CPU的執行效率，減少因程序等待帶來的CPU空轉以及其他計算機軟硬件資源而提出來的。進程是一個資源擁有者，因而在進程的創建、撤消和切換中，系統必須為之付出較大的時空開銷。也正因

線程間的通信、同步方式與進程間通信方式

結果 全局變量 應用程序 聲明 是否 請求 bsp 方式 可能 1.線程間的通信方式 1)使用全局變量(由於多個線程可能更改全局變量,因此全局變量最好聲明為volatile) 2) 使用消息實現通信 3)使用事件CEvent類實現線程間的通信 2.同步/異步(C端) 同步

35、concurrent.futures模塊與協程

否則 ssp org 之間 內存 pat sta page hide concurrent.futures —Launching parallel tasks concurrent.futures模塊同時提供了進程池和線程池，它是將來的使用趨勢，同樣我們之前學習的進

Java面試18|關於進程、線程與協程

消息隊列 受限 ctu 方法調用 套接字 pro 最快 remote sina 1、IPC（Inter-Process Communication，進程間通信）與線程通信的幾種方式 # 管道( pipe )：管道是一種半雙工的通信方式，數據只能單向流動，而且只能在具

java代理模式與裝飾者模式

對象 tro 來看 彈性 java代理 question 設計模式 ava 設計 靜態代理和裝飾者模式的區別： 　　先來看一下裝飾者模式的定義:裝飾者模式動態地將責任附加到對象上。若要擴展功能，裝飾者提供了比繼承更有彈性的替代方案。 　　總結一下采用裝飾者模式是為了增強或拓

說說html 的<!DOCTYPE>聲明&標準模式與兼容模式

ffffff get 建議 highlight lns 標準 round div spa 我們都知道<!DOCTYPE>聲明位於文檔的最前面，處於<html>標簽之前。 <!DOCTYPE>聲明不是html標簽，它的作用：告知web瀏覽界

大端模式與小端模式

abcde 輸出 stdlib.h rto bcd lib 字符 小端 const Big-Endian和Little-Endian的定義如下： 1) Little-Endian就是低位字節排放在內存的低地址端，高位字節排放在內存的高地址端。 2) Big-Endi

抽象工廠模式與工廠方法模式的區別

dma ati ring factor elf ride 測試 string this 　　抽象工廠模式與工廠方法模式的最大區別在於，工廠方法模式針對的是一個產品等級結構；而抽象工廠模式則需要面對多個產品等級結構。 　　在什麽情況下應當使用抽象工廠模式？ 　　這個系統的產品

生成器與協程 | Python

while close got def style for 停止 () 使用 # 生成器與協程 # 生成器是一種特殊的叠代器,它同樣生成一個值的序列; # 如何定義生成器？ # 方法一：函數中使用yield關鍵字; class count_down(n):

閉包(closure)與協程共用時要註意的事情

閉包函數 rac 外部 它的 有意 ret 漸進 true strong 閉包是一種能夠讓你用非常舒服的方式來編程的小技巧，Go也支持閉包。假設從來沒有接觸過閉包，

4月28日 python學習總結 線程與協程

回調 obj eat dom print 返回 ces cal 保存 一、 異步與回調機制　　 問題： 1、任務的返回值不能得到及時的處理，必須等到所有任務都運行完畢才能統一進行處理 2、解析的過程是串行執行的,如果解析一次需要花費2s,解析9次則需要花費18s 解決

簡單工廠模式與工廠方法模式

interface ace nal tor sim str bre sys 對象比較 簡單工廠 定義：簡單工廠模式屬於創建型模式，其又被稱為靜態工廠方法模式，這是由一個工廠對象決定創建出哪一種產品類的實例 工廠類 public class CamputerFacto

回撥與協程

回撥: 通常回調是以向一個方法傳遞另一個函式作為引數, 在該方法中, 於適當的時候呼叫傳遞的函式引數的形式呈現的, 回撥的本質還是函式呼叫, 他與普通的函式呼叫的不同點在於, 普通的函式呼叫在程式設計時已經確定要呼叫哪個函式, 而回調機制是在執行時確定需要呼叫的函式的, 根據傳遞的作為引數的函式不同, 其行

程序、執行緒與協程

程序 程序的出現是為了更好的利用CPU資源使到併發成為可能。 假設有兩個任務A和B，當A遇到IO操作，CPU默默的等待任務A讀取完操作再去執行任務B，這樣無疑是對CPU資源的極大的浪費。聰明的老大們就在想若在任務A讀取資料時，讓任務B執行，當任務A讀取完資料後，再切換到任務A執行。注意關