Another look at amazon EBS storage performance

Lately I've gave up bonnie++ in favor of iozone. I've done lot of performance checks on hardware I've got in my hands. That also means that I have to check iozone performance on my amazon instances.

Since tested instance was t1.micro, 1Gb test file was enough to avoid false cache results.

So command run was:

./iozone -a -i0 -i1 -i2 -r4k -O -n1g -g1g

Bonnie++ results database

Finally I've just found small amount of time to write 2 PHP scripts and create database with all bonnie++ results I've got. All tests were run by me. Some tests do not have character speeds (those got -1 value there). You can sort results by: block write speed, character write speed, rewrite, block read speed, character read speed and seeks. You can also narrow results down by filtering LVM, encryption and filesystem type. Every new bonnie++ runs gonna go there.

Hope some of you gonna find this useful. Link is http://bonnie.it64.com/

Linux software raid with 2-6 disks ext3/ext4 performance tests.

Lately I've got 6 500GB SATA 7200 rpm disks in my hands. So I decided to do some performance tests of linux software raid.
There are a lot of legends about raid levels, which are better for database or file storing. Also there are informations how much which raid layout loads CPU.
So I decided to verify those.

Ext3 / ext4 extended options with soft raid and simple performance tests.

I guess almost every linux admin heard that when you creating ext filesystem over software raid you should consider using extended mkfs options. Two important options for that operation are: stride and stipe-width, which you should calculate for your setup of raid (number of disks, level, chunk size). You can calculate all those parameters each time you create ext2/ext3/ext4, but there are lot of ready calculators to use. I'd prefer using this one. Cause it's simple and fast.

Subscribe to RSS - ext4

Main menu

by Dr. Radut