Need assistance with IOMeter

[peanuthead]

For grins and giggles I decided to see what the IOPs were from a NAS I have and I'm getting some weird numbers. I'm getting numbers like 2K IOPS from a 6 disk SATA 7.2k RAID 5. I will start at ~600 IOPS then jumps to the 2K range and bounces around there. My hunch is that IOMeter is pulling from RAM/some sort of caching is going on. Thoughts anyone?

 

[NetJunkie]

What's your test file size? What's your benchmark? I can easily pull over that with IOMeter with a sequential test..or out of RAM.

 

[peanuthead]

First, I'm IOmeter ignorant. Not sure how to really answer your question honestly. I am using the steps outlined here http://media.community.dell.com/en/dtc/attach/installing and using iometer under windows.pdf
and here
http://greg.porter.name/wiki/HowTo:iometer

 

[NetJunkie]

Which Access Profile are you choosing?

 

[peanuthead]

I was using All in One, 32K 100% read, 0% random and 32K 0% read, 0% random.

 

[NetJunkie]

That's all sequential so you'll see very high I/O. Throw some random in to it and see what happens. 32KB I/Os are big, too.

 

[lopoetve]

Big-ish. Getting WAY more common though

 

[peanuthead]

Still seeing over 3K IOPs with about 35ms latency according to the display tab. Perhaps I am deciphering the output incorrectly. I get the same results using 1 worker or 10 workers.

 

[lopoetve]

how much random did you set? Try 100%.

 

[peanuthead]

That was at 100%.

https://dl.dropboxusercontent.com/u/14072811/results2.csv

 

[NetJunkie]

Increase the test file size. I'd say it's sitting in cache.

 

[peanuthead]

That is what it was. I took the file size to 128K chunks and set 3 worker threads and started to pull about 580-590 IOPs. That's about where I expected it to be. The lowest I saw was 520 IOPs for 1MB chunks.

 

[lopoetve]

Yeah, I run mine 7x18G samples to ~never~ fit in cache.