There are plenty of benchmarking tools available but storage professionals mostly use IOmeter. Unfortunately IOmeter is a little tricky to use. You really need to read the user manual first. I have frequently seen users trying to run IOmeter tests without success. Being human, most of us hate to read the manual and with IOmeter this can lead to problems. I hope this short post will help you to get the wanted results. First off, you need to know that IOmeter recognizes 2 different volume types:
• un-partitioned disks (blue icon disk), or
• formatted disks (yellow icon with a red slash though it)
With un-partitioned disks you can start the test at once, but to run with formatted disks you need a test file. The test file must be placed in the root directory and named: iobw.tst. By default IOmeter will create the test file if not found. The problem is that nowadays volumes are very big, and IOmeter runs very slowly. It’s much faster to create the test file using the TestFileCreator.exe from Open-E. Please run it in order to create iobw.tst with any size you desire. You can run: TestFileCreator.exe 100G in order to create a file of exactly 100GB.
So, if your goal is to obtain the maximum MB/sec please create a test set up with 2-4 workers, using a block size of 256k and 100% sequential read or write. In our case the sequential read shows the best result: 772 MB/sec! Please make your settings very carefully and make sure all workers use the same test configuration! If you forget to add your [256kB, 100% sequential read] configuration to every worker you will be surprised with very low results because the default test settings use 2kB block and mixed random/sequential and read/write pattern. So instead of the desired 772MB/sec you might see 100 times less, i.e. ~ 7MB/sec.