普通磁碟與LSI快閃記憶體卡測試對比
歡迎轉載,請註明作者、出處。
Sysbench測試:
測試環境:
工具:sysbench 0.4.12
Mysql 5.6.15
Innodb buffer pool:2G
本次測試,資料量:11.7G
注:以下所提及到的本地硬碟,為raid儲存劃分到本地的空間。
準備資料:
sysbench --debug=off --test=oltp --mysql-table-engine=innodb --oltp-table-size=50000000 --mysql-user=root --mysql-password=mysql --mysql-socket=/lsi/mysql/mysql.sock prepare
說明:模擬OLTP操作,資料量5000萬行,每行記錄252Byte。
LSI:
sysbench --num-threads=256 --test=oltp --mysql-user=root --mysql-password=mysql --mysql-table-engine=innodb --init-rng=on --oltp-table-size=50000000 --max-time=$RT --max-requests=1000000 --mysql-socket=/lsi/mysql/mysql.sock run > sysbench.log
說明:併發256,儲存引擎innodb
執行過程中,CPU與LSI卡的情況:
說明:併發較大,CPU較繁忙,但是IO不是太busy,說明瓶頸不在IO上。
最終結果:
Initializing random number generator from timer.
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations, 1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Using auto_inc on the id column
Maximum number of requests for OLTP test is limited to 1000000
Threads started!
Done.
OLTP test statistics:
queries performed:
read: 14014098
write: 5005024
other: 2002010
total: 21021132
transactions: 1001003 (3445.66 per sec.)
deadlocks: 4 (0.01 per sec.)
read/write requests: 19019122 (65467.84 per sec.)
other operations: 2002010 (6891.34 per sec.)
Test execution summary:
total time: 290.5109s
total number of events: 1001003
total time taken by event execution: 74348.2259
per-request statistics:
min: 3.41ms
avg: 74.27ms
max: 756.14ms
approx. 95 percentile: 144.95ms
Threads fairness:
events (avg/stddev): 3910.1680/32.56
execution time (avg/stddev): 290.4228/0.01
本地盤:
sysbench --num-threads=256 --test=oltp --mysql-user=root --mysql-password=mysql --mysql-table-engine=innodb --init-rng=on --oltp-table-size=50000000 --max-time=$RT --max-requests=1000000 --mysql-socket=/var/lib/mysql/mysql.sock run > sysbench.log
執行過程中磁碟與CPU情況:
說明:與LSI儲存卡相比,本地磁碟進行OLTP模擬測試時,CPU相對空閒,IO成為瓶頸。
最終結果:
Initializing random number generator from timer.
Doing OLTP test.
Running mixed OLTP test
Using Special distribution (12 iterations, 1 pct of values are returned in 75 pct cases)
Using "BEGIN" for starting transactions
Using auto_inc on the id column
Maximum number of requests for OLTP test is limited to 1000000
Threads started!
Done.
OLTP test statistics:
queries performed:
read: 14013118
write: 5004682
other: 2001873
total: 21019673
transactions: 1000936 (959.86 per sec.)
deadlocks: 1 (0.00 per sec.)
read/write requests: 19017800 (18237.34 per sec.)
other operations: 2001873 (1919.72 per sec.)
Test execution summary:
total time: 1042.7948s
total number of events: 1000936
total time taken by event execution: 266923.0217
per-request statistics:
min: 3.46ms
avg: 266.67ms
max: 6884.36ms
approx. 95 percentile: 649.23ms
Threads fairness:
events (avg/stddev): 3909.9062/30.04
execution time (avg/stddev): 1042.6681/0.03
結論:使用LSI快閃記憶體卡後,MySQL的TPS提升了260%。其實本測試中的磁碟也是相當高階的儲存,一般磁碟達不到這個數(具體配置我記不清了,可透過下面的IOPS可以看出來)
FIO測試:
進行8K的隨機讀,測試時間為10分鐘
LSI:
fio tmp.txt
tmp.txt
[global]
direct=1
iodepth=32
ioengine=libaio
norandommap
randrepeat=0
numjobs=128
runtime=600
ramp_time=60
thread
group_reporting
name=mytest
[randread]
filename=/dev/sda1
bs=8k
rw=randread
說明:FIO測試是直接對儲存裝置進行讀寫
最終結果:
[1123MB/0KB/0KB /s] [144K/0/0 iops] [eta 00m:00s]
mytest: (groupid=0, jobs=128): err= 0: pid=9514: Fri Jan 17 15:30:26 2014
read : io=671818MB, bw=1119.7MB/s, iops=143310, runt=600015msec
slat (usec): min=3, max=136762, avg=871.03, stdev=4018.21
clat (usec): min=77, max=237967, avg=27708.34, stdev=11974.67
lat (usec): min=83, max=237985, avg=28578.69, stdev=12253.82
clat percentiles (usec):
| 1.00th=[ 1608], 5.00th=[16768], 10.00th=[17792], 20.00th=[19328],
| 30.00th=[20352], 40.00th=[21376], 50.00th=[22400], 60.00th=[25984],
| 70.00th=[35072], 80.00th=[37632], 90.00th=[40704], 95.00th=[45824],
| 99.00th=[63744], 99.50th=[75264], 99.90th=[94720], 99.95th=[101888],
| 99.99th=[125440]
bw (KB /s): min= 0, max=12931, per=0.78%, avg=8957.79, stdev=980.34
lat (usec) : 100=0.01%, 250=0.01%, 500=0.01%, 750=0.01%, 1000=0.05%
lat (msec) : 2=1.96%, 4=0.70%, 10=0.01%, 20=24.54%, 50=68.30%
lat (msec) : 100=4.39%, 250=0.06%
說明:60%的延遲在50ms
cpu : usr=0.39%, sys=2.42%, ctx=6605219, majf=0, minf=8200
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=109.8%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
issued : total=r=85988683/w=0/d=0, short=r=0/w=0/d=0
Run status group 0 (all jobs):
READ: io=671818MB, aggrb=1119.7MB/s, minb=1119.7MB/s, maxb=1119.7MB/s, mint=600015msec, maxt=600015msec
Disk stats (read/write):
sda: ios=94385676/0, merge=110/0, ticks=207649589/0, in_queue=207374825, util=100.00%
本地盤:
[global]
direct=1
iodepth=32
ioengine=libaio
norandommap
randrepeat=0
numjobs=128
runtime=600
ramp_time=60
thread
group_reporting
name=mytest
[randread]
filename=/dev/cciss/c0d0p2
bs=8k
rw=randread
最終結果:
[19083KB/0KB/0KB /s] [2385/0/0 iops] [eta 18h:41m:14s]
mytest: (groupid=0, jobs=128): err= 0: pid=18257: Sun Mar 31 06:17:48 2013
read : io=3708.1MB, bw=6300.2KB/s, iops=780, runt=602834msec
slat (usec): min=5, max=5489.7K, avg=162593.81, stdev=906297.12
clat (usec): min=29, max=10575K, avg=5068121.79, stdev=1001568.61
lat (usec): min=40, max=15858K, avg=5231354.46, stdev=1336481.76
clat percentiles (msec):
| 1.00th=[ 29], 5.00th=[ 5145], 10.00th=[ 5145], 20.00th=[ 5211],
| 30.00th=[ 5211], 40.00th=[ 5276], 50.00th=[ 5276], 60.00th=[ 5276],
| 70.00th=[ 5342], 80.00th=[ 5342], 90.00th=[ 5342], 95.00th=[ 5407],
| 99.00th=[ 5473], 99.50th=[ 5473], 99.90th=[ 5538], 99.95th=[ 5538],
| 99.99th=[ 5538]
bw (KB /s): min= 0, max= 1158, per=0.78%, avg=48.88, stdev=19.10
lat (usec) : 50=0.01%, 100=0.01%, 250=0.02%, 500=0.04%, 750=0.01%
lat (usec) : 1000=0.01%
lat (msec) : 4=0.01%, 10=0.09%, 20=0.43%, 50=1.32%, 100=1.31%
lat (msec) : 250=0.22%, 500=0.05%, 750=0.07%, 1000=0.07%, 2000=0.16%
lat (msec) : >=2000=97.03%
說明:97.03%的延遲在2000ms以上
cpu : usr=0.00%, sys=0.01%, ctx=35292, majf=0, minf=8198
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.2%, 16=0.4%, 32=109.1%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
issued : total=r=470774/w=0/d=0, short=r=0/w=0/d=0
Run status group 0 (all jobs):
READ: io=3708.1MB, aggrb=6300KB/s, minb=6300KB/s, maxb=6300KB/s, mint=602834msec, maxt=602834msec
Disk stats (read/write):
cciss!c0d0: ios=517653/321, merge=0/717, ticks=96165858/457, in_queue=96178286, util=99.94%
LSI、本地磁碟結果比較:
LSI的IOPS為:144k,本地硬碟IOPS為2385,LSI儲存卡速度明顯高於本地磁碟。而且,LSI延遲較低,大部分延遲在50ms,而本地磁碟97%的延遲在2000ms。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26355921/viewspace-1248098/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 關於快閃記憶體磁碟記憶體
- 快閃記憶體卡型別記憶體型別
- 遊戲記憶體對比普通記憶體區別 遊戲記憶體和普通記憶體相差大嗎?遊戲記憶體
- 快閃記憶體盤和普通u盤哪個好 快閃記憶體盤和u盤的區別記憶體
- Glide - 記憶體快取與磁碟快取IDE記憶體快取
- 序列SPI NOR快閃記憶體VS並行NOR快閃記憶體記憶體並行
- 十六、FLASH快閃記憶體記憶體
- 快閃記憶體請將磁碟插入驅動器如何解決記憶體
- Wikibon:資料中心快閃記憶體取代磁碟要多久?記憶體
- 記憶體快取系統memcached與redis實現的對比記憶體快取Redis
- 用 VeraCrypt 加密快閃記憶體盤加密記憶體
- 惠普成功測試記憶體電腦 比傳統電腦快8000倍記憶體
- 記憶體條頻率越高越好嗎?高低頻率DDR4記憶體條效能測試對比記憶體
- 遊戲記憶體測試遊戲記憶體
- Marvell公司在快閃記憶體峰會上展示行業領先的快閃記憶體創新解決方案記憶體行業
- CMR:2019年Q1印度快閃記憶體卡市場下降20%記憶體
- CMR:過去5年印度消費者快閃記憶體卡容量增長3倍記憶體
- NVMe :一個快閃記憶體時代的引爆點記憶體
- laravel redirect快閃記憶體blade讀取不到Laravel記憶體
- 宏旺科普貼:手機國產記憶體晶片、快閃記憶體晶片怎麼區分與選購?記憶體晶片
- 磁碟資料庫與記憶體資料庫的特點比較資料庫記憶體
- iPhone7用TLC快閃記憶體:蘋果不厚道?iPhone記憶體蘋果
- Fuzzm: 針對WebAssembly記憶體錯誤的模糊測試Web記憶體
- 記憶體洩漏與記憶體溢位神比較記憶體溢位
- 記憶體與IO,磁碟IO,網路IO記憶體
- 為什麼暫存器比記憶體快?記憶體
- Win10神秘加成? 磁碟讀寫效能對比測試Win10
- 記憶體管理與檢測記憶體
- NOR快閃記憶體開始汽車領域的發展記憶體
- 你真的懂HTML嗎-從”最新快閃記憶體”說起HTML記憶體
- 記憶體資料庫解析與主流產品對比(三)記憶體資料庫
- 記憶體資料庫解析與主流產品對比(二)記憶體資料庫
- 記憶體資料庫解析與主流產品對比(一)記憶體資料庫
- 軟體測試學習教程——WEB測試之JS記憶體WebJS記憶體
- 綠色資料時代,全快閃記憶體與資料中心的註定邂逅記憶體
- 查詢windows記憶體卡槽及卡槽支援的最大記憶體Windows記憶體
- openGauss 對比-磁碟與MOT
- 反射記憶體卡的優勢與特點反射記憶體