每準備使用新東西前需要考慮它有什么功能鹅很，耐不耐用嘶居，性能好不好，不盲目追新，也不無緣無故排斥邮屁。
主要任務(wù)
一：Docker中IO整袁、MariaDB的性能測試
二：并宿主機進行對比
Docker version 1.12.1
操作系統(tǒng)：CentOS7.2
內(nèi)存：32G
CPU：Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz 1顆6核
- Docker中磁盤IO的性能測試
sysbench --test=fileio --file-num=16 --file-block-size=16384 --file-total-size=2G --num-threads=4 --file-test-mode=rndrd --max-requests=100000000 --max-time=180 --file-extra-flags=direct prepare
sysbench --test=fileio --file-num=16 --file-block-size=16384 --file-total-size=2G --num-threads=4 --file-test-mode=rndrd --max-requests=100000000 --max-time=180 --file-extra-flags=direct run
#其他類型的讀寫-只要改成file-test-mode即可seqwr 順序?qū)?、seqrewr 連續(xù)改寫 佑吝、seqrd 連續(xù)讀 坐昙、rndrd 隨機讀取 、rndwr 隨機寫 芋忿、rndrw 結(jié)合隨機讀/寫
sysbench --test=fileio --file-num=16 --file-block-size=16384 --file-total-size=2G --num-threads=4 --file-test-mode=rndrd --max-requests=100000000 --max-time=180 --file-extra-flags=direct cleanup
重要：測試寫不需要準備數(shù)據(jù)炸客，測試讀時一定要將文件數(shù)據(jù)都準備好。
Paste_Image.png
-
Docker中MariaDB的性能測試
本地磁盤和docker掛載磁盤上mariaDB的性能比較
Sysbench OLTP read only compare.jpg
Sysbench OLTP read-write compare.jpg可以看出在docker上運行的性能比本地要差點痹仙，但差別的數(shù)據(jù)在可接受范圍內(nèi)。
有興趣的同學-還可以順帶測試下memory和cpu逆趣，我得到結(jié)果是native是稍微比docker差點蝶溶，支持這個理論依據(jù)是什么？看來是時候重讀理論啦宣渗。
sysbench --test=memory --num-threads=16 --memory-block-size=8192 --memory-total-size=8G run
sysbench --test=cpu --cpu-max-prime=20000 run
#native
sysbench 0.5: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Random number generator seed is 0 and will be ignored
Prime numbers limit: 20000
Initializing worker threads...
Threads started!
General statistics:
total time: 56.4280s
total number of events: 10000
total time taken by event execution: 56.4238s
response time:
min: 5.46ms
avg: 5.64ms
max: 7.52ms
approx. 95 percentile: 5.65ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 56.4238/0.00
#docker
sysbench 0.5: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Random number generator seed is 0 and will be ignored
Prime numbers limit: 20000
Initializing worker threads...
Threads started!
General statistics:
total time: 56.0816s
total number of events: 10000
total time taken by event execution: 56.0777s
response time:
min: 5.60ms
avg: 5.61ms
max: 7.52ms
approx. 95 percentile: 5.61ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 56.0777/0.00
