，歡迎訪問網頁設計愛好者web開發。
原文鏈接:
http://www.eygle.com/unix/use.bonnie++.to.test.io.speed.htm
由于bonnie存在一些眾所周知的問題,比如>2g的文件支持.
russell coker ([email protected]) 開發了一套新的代碼,用以支持>2g的文件等.
得到tim bray ([email protected])的許可之后,russell把他的軟件命名為bonnie++,在網上發布,并開始流行起來.
目前的版本已經更新到了1.03a,你可以到以下地址下載:
http://www.coker.com.au/bonnie++/
你也可以點擊這里下載,這個版本需要編譯,如果你沒有編譯環境,可以點擊這里下載我編譯好的,適用于sun solaris環境(solaris8測試通過)
russell coker的個人主頁是:
http://www.coker.com.au/
bonnie++ 與 bonnie的區別主要是:
http://www.coker.com.au/bonnie++/diff.html
我簡單介紹一下bonnie++的編譯及使用:
1.編譯
你需要把以上下載的源碼編譯以后才能使用,如果你沒有編譯環境,可以點擊這里下載我編譯好的,適用于sun solaris環境(solaris8測試通過)
當然你需要安裝make,及gcc等必要編譯器.在編譯過程中,如果遇到以下錯誤,可能是因為你沒有設置正確的環境變量
$ ./configure
grep: illegal option -- q
usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
usage: grep -hblcnsviw pattern file . . .
checking for g++... g++
checking for c++ compiler default output... a.out
checking whether the c++ compiler works... configure: error: cannot run c++ compiled programs.
if you meant to cross compile, use `--host'.
see `config.log' for more details.
設置環境變量后繼續編譯,一般可以成功.
# export ld_library_path=/usr/lib:/usr/local/lib
# ./configure
grep: illegal option -- q
usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
usage: grep -hblcnsviw pattern file . . .
checking for g++... g++
checking for c++ compiler default output... a.out
checking whether the c++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the gnu c++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the c++ preprocessor... g++ -e
checking for a bsd-compatible install... /usr/bin/install -c
checking for an ansi c-conforming const... yes
checking for egrep... egrep
checking for ansi c header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking for size_t... yes
checking vector.h usability... yes
checking vector.h presence... yes
checking for vector.h... yes
checking vector usability... yes
checking vector presence... yes
checking for vector... yes
checking algorithm usability... yes
checking algorithm presence... yes
checking for algorithm... yes
checking algo.h usability... yes
checking algo.h presence... yes
checking for algo.h... yes
checking algo usability... no
checking algo presence... no
checking for algo... no
configure: creating ./config.status
config.status: creating makefile
config.status: creating bonnie.h
config.status: creating port.h
config.status: creating bonnie++.spec
config.status: creating bon_csv2html
config.status: creating bon_csv2txt
config.status: creating sun/pkginfo
config.status: creating conf.h
config.status: conf.h is unchanged
編譯完成之后會生成bonnie++,可以用來測試了.
2.下面是一些測試結果
a.t3大文件讀寫測試
# ./bonnie++ -d /data1 -u root -s 4096 -m billingusing uid:0, gid:1.writing with putc()...donewriting intelligently...donerewriting...donereading with getc()...donereading intelligently...donestart 'em...done...done...done...create files in sequential order...done.stat files in sequential order...done.delete files in sequential order...done.create files in random order...done.stat files in random order...done.delete files in random order...done.version 1.03 ------sequential output------ --sequential input- --random- -per chr- --block-- -rewrite- -per chr- --block-- --seeks--machine size k/sec %cp k/sec %cp k/sec %cp k/sec %cp k/sec %cp /sec %cpbilling 4g 9915 87 30319 56 11685 38 9999 99 47326 66 177.6 3 ------sequential create------ --------random create-------- -create-- --read--- -delete-- -create-- --read--- -delete-- files /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp 16 639 19 +++++ +++ 1258 22 679 16 +++++ +++ 1197 27billing,4g,9915,87,30319,56,11685,38,9999,99,47326,66,177.6,3,16,639,19,+++++,+++,1258,22,679,16,+++++,+++,1197,27
b. emc clariion cx500 測試數據
這個是在我禁用了寫cache以后的測試數據:
4塊盤的raid1+0測試:
# ./bonnie++ -d /eygle -u root -s 4096 -m jump using uid:0, gid:1.file size should be double ram for good results, ram is 4096m.# ./bonnie++ -d /eygle -u root -s 8192 -m jumpusing uid:0, gid:1.writing with putc()...donewriting intelligently...donerewriting...donereading with getc()...donereading intelligently...donestart 'em...done...done...done...create files in sequential order...done.stat files in sequential order...done.delete files in sequential order...done.create files in random order...done.stat files in random order...done.delete files in random order...done.version 1.03 ------sequential output------ --sequential input- --random- -per chr- --block-- -rewrite- -per chr- --block-- --seeks--machine size k/sec %cp k/sec %cp k/sec %cp k/sec %cp k/sec %cp /sec %cpjump 8g 12647 36 13414 8 7952 13 33636 97 146503 71 465.7 5 ------sequential create------ --------random create-------- -create-- --read--- -delete-- -create-- --read--- -delete-- files /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp 16 86 1 +++++ +++ 161 1 81 1 +++++ +++ 163 1jump,8g,12647,36,13414,8,7952,13,33636,97,146503,71,465.7,5,16,86,1,+++++,+++,161,1,81,1,+++++,+++,163,1
4塊盤的raid5,禁用寫cache后的速度:
# ./bonnie++ -d /eygle -u root -s 8192 -m jumpusing uid:0, gid:1.writing with putc()...donewriting intelligently...donerewriting...donereading with getc()...donereading intelligently...donestart 'em...done...done...done...create files in sequential order...done.stat files in sequential order...done.delete files in sequential order...done.create files in random order...done.stat files in random order...done.delete files in random order...done.version 1.03 ------sequential output------ --sequential input- --random- -per chr- --block-- -rewrite- -per chr- --block-- --seeks--machine size k/sec %cp k/sec %cp k/sec %cp k/sec %cp k/sec %cp /sec %cpjump 8g 10956 30 10771 6 3388 5 34169 98 158861 75 431.1 5 ------sequential create------ --------random create-------- -create-- --read--- -delete-- -create-- --read--- -delete-- files /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp /sec %cp 16 81 1 +++++ +++ 160 1 82 1 +++++ +++ 109 1jump,8g,10956,30,10771,6,3388,5,34169,98,158861,75,431.1,5,16,81,1,+++++,+++,160,1,82,1,+++++,+++,109,1
對比這兩個結果我們發現(單位k/sec):
字符寫block寫字符讀block讀raid1012,64713,41433,636146,503raid510,95610,77134,169158,861diff1,6912,643-533-12,358
我們看到,在直接讀寫上,寫raid10會略快于raid5;而在讀取上,raid5會略快于raid10,這符合我們通常的觀點.
這里需要提一下的是,通常我們建議把redolog file存放在raid10的磁盤上,因其具有寫優勢.
