What the best way to test IOPS?
-
@scottalanmiller said:
@aaronstuder said:
I am getting about 6000 IOPS on 3 960GB SSD drives.
6K? Not 600K?
LOl - this number seemed really low to me as well.
I think the SSD in my home machine delivers something like 70,000 IOPs.
-
@Dashrender said:
@scottalanmiller said:
@aaronstuder said:
I am getting about 6000 IOPS on 3 960GB SSD drives.
6K? Not 600K?
LOl - this number seemed really low to me as well.
I think the SSD in my home machine delivers something like 70,000 IOPs.
My last one was listed at 100K.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@aaronstuder said:
I am getting about 6000 IOPS on 3 960GB SSD drives.
6K? Not 600K?
LOl - this number seemed really low to me as well.
I think the SSD in my home machine delivers something like 70,000 IOPs.
My last one was listed at 100K.
Exactly - my home one is older. 90K+ is very common today - in a 3 drive RAID 5, I would expect to get at least 1.5 times a single drive, if not a lot more.
-
I am getting my numbers from Veeam One. This is the number of IOPS we are getting, not the max.... How do I figure out the max?
-
This post is deleted! -
@aaronstuder said:
I am getting my numbers from Veeam One. This is the number of IOPS we are getting, not the max.... How do I figure out the max?
You need to run something like IOMeter. That tool can create loads on your server to simulate real workloads. then it will tell you what it saw for available IOPs.
It's best to do this with nothing else running on the hardware, except the OS that's running IOMeter.
-
@Dashrender Does it run on linux?
-
-
This program is from 2006.....
-
@aaronstuder said:
This program is from 2006.....
Not sure where you get this.. It was updated in 2014.
-
@aaronstuder said:
This program is from 2006.....
And? Spinrite hasn't been updated since something like 2001, and it's still nearly the best if not the best HD utility on the market for consumers and businesses alike.
When a tool works, why mess with it?
-
@Dashrender said:
@aaronstuder said:
This program is from 2006.....
And? Spinrite hasn't been updated since something like 2001, and it's still nearly the best if not the best HD utility on the market for consumers and businesses alike.
When a tool works, why mess with it?
It's not from 2006 anyway, he must be looking at the old versions not the current.
-
@aaronstuder said:
I am getting my numbers from Veeam One. This is the number of IOPS we are getting, not the max.... How do I figure out the max?
Ah, that's the number "you are able to use".
The max would be best just grabbed from the device specs. IOPS aren't a simple number like you imagine. You talk about IOPS in many different ways. The things that you do dramatically change how many IOPS you can get from your devices.
-
-
Be warned, testing IOPS requires overwriting the drives. So any test that tests your IOPS has to blow away your storage. If it doesn't, it's not even remotely a useful test. So think carefully before doing this on anything that isn't a fresh build.
-
@scottalanmiller said:
Be warned, testing IOPS requires overwriting the drives. So any test that tests your IOPS has to blow away your storage. If it doesn't, it's not even remotely a useful test. So think carefully before doing this on anything that isn't a fresh build.
But you can run it inside the OS that's on those drives without concern that that data already there will be damaged.
-
@aaronstuder said:
???
Oracle VDBench and Intel I/O Meter (this one will require custom settings to test against "smart" storage doing cache and dedupe).
-
@Dashrender said:
@scottalanmiller said:
Be warned, testing IOPS requires overwriting the drives. So any test that tests your IOPS has to blow away your storage. If it doesn't, it's not even remotely a useful test. So think carefully before doing this on anything that isn't a fresh build.
But you can run it inside the OS that's on those drives without concern that that data already there will be damaged.
That's not testing Max IOPS though, that's testing what IOPS you use.
-
@Dashrender said:
@scottalanmiller said:
Be warned, testing IOPS requires overwriting the drives. So any test that tests your IOPS has to blow away your storage. If it doesn't, it's not even remotely a useful test. So think carefully before doing this on anything that isn't a fresh build.
But you can run it inside the OS that's on those drives without concern that that data already there will be damaged.
Sure... but since that doesn't test what is in question, there wouldn't be any point to that.
