Disk Performance

22 Jun

Different ways to check disk performance

It can be run like:
/usr/local/bonnie++-1.03a/sbin/bonnie++ -d /tmp -s 3000 -m jekyll -r 1024 -x 4 -u 12135 > bonnie_out

-d /tmp = write to /tmp
-s 3000 = use 3000meg file
-r 1024 = i have 1024meg ram
-x 4 = run 4 tests
-u 12135 = run with uid=12135 (iisjsoo)

This directs the output (which is CSV) to a file called bonnie_out. For nice output of this run: /usr/local/bonnie++-1.03a/bin/bon_csv2txt < bonnie_out

(if you get '++++' in output it means that the test didn't run long enough to get an accurate result – increase the file size you're using)

Note that this will put a fair bit of load on the system (running 3 gig test files will take 20mins+). Perhaps we should run these as cron jobs in the middle of the night? (we could actually do it on a number of machines and see how performance moves over time)

I guess the idea for Jekyll is to run it on /tmp and compare it to running it on /mnt/share or /mnt/home.

For Linus i get something like:
-bash-2.05b$ /usr/local/bonnie++-1.03a/bin/bon_csv2txt 1m18 secs to write an 8Gigabyte file => approx. 105 Mbytes/sec for
write. That’s OK.

If you then do the following to read the file back from the RAID0 Drive:

testpenguin1# time dd if=/storage/hugetest of=/dev/null bs=256k
32768+0 records in
32768+0 records out

real 12m32.292s
user 0m0.210s
sys 0m53.180s

it takes an AMAZING 12m32secs => 752 secs to read 8Gigabytes. That is
equivalent to 10.88 Mbyte/sec performance!
hdparm -tT /dev/sda
hdparm -tT /dev/hda


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: