I am using this data to perform some calculations and so far I have found different answers or no answers. Grant it, IOPS will be dependent on block size, but I am looking for average numbers that I can plug in.

Note that the high figures assume a real-world true random workload. You would get better numbers if you used techniques such as short-stroking drives or tuned benchmarks purely to get the best numbers possible. I use the average numbers for sizing storage arrays as it gives you burst capacity.

SSD rules the "IOPS usage" world...
The only IOPS situation where using HDD may be a good idea is when you NEED a multipath feature allowing for TWO IO controller to be plugged in each drive. Rare SSD has this "dual-port" feature at a very expensive cost.

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

As you may have figured out, this is for a VDI implementation. I know that "WriteIOPS" is the big killer when it comes to a virtualization initiative. The calculations I am performing are based on the Write IOPS value of the drive, minus the raid penalty. From there I am using an average IOPS number for the VD at Normal usage (about 7-8 IOPS). This will tell me how many VD's I can support on a single drive.

Am I on the right track here or should I be using the total Random IOPS value for this?

Another question I have is that from everything I have seen and researched, the size of the drive has nothing to do with IOPS!?

No matter if you have a 300GB or a 750GB drive, if they are both 10K, you are only using the RPM speed, average seek time and R/W latency to calculate IOPS.

BigSchmuh:
I like the SSD drives and they are very appealing because of the IOPS they are able to support, however... If I had a 5000 IOPS requirement for a VDI, one (1) SSD could provide all the IOPS I need.

From my example above, VD = 8 IOPS, Total IOPS needed = 5000

5000 / 8 = 625 VD's

Each VD is 15GB + 3GB Persistent Disk = 18GB Total per VD.

18 * 625 = 11.250 TB or data storage needed.

I would have to purchase 24 - 500GB SSD's or 12 - 1TB SSD's in order to accomodate the storage needs that the VD's will need. This would be IOPS overload... grant it, there would never be a latency issue, but at the cost, it just isn't practical.

Then divide IOPS per drive into total IOPS for the total number of drives. Don't forget to round up to the nearest even number if you're using RAID 1/0. Also Note that the total includes parity drives as they participate in providing performance.

This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target.
To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting.
This w…