It's been a while since IOMeter was updated. IOMeter 1.1 has some huge code changes according to the user guide. There are some some bug fixes as well in this new release. Important to note that if comparing the same workload between two different versions of IOMeter, you might not get the same results. It's because of the fixes in the new release.
I never really paid attention who was the original developer, but today as I blog about the product it you might find it interesting as IOMeter (Iometer and Dynamo executable) is distributed as part of an Intel Opensource License. The original project back in 1998 was brought to life by Intel. There are other independent IOMeter modules which are distributed as GNU Public license. (ex. the iomtr_kstat kernel module).
Quote from IOMeter.org site:
It was originally developed by the Intel Corporation and announced at the Intel Developers Forum (IDF) on February 17, 1998 – since then it got wide spread within the industry.
IOMeter's documentation has been updated to match the 1.1 release as well.
What's New in IOMeter 1.1?
What's New in IOMeter 1.1?- New features – Enormous code changes due to code cleanup and portability enhancements.
- Bug fixes – fixed the 2 GB limit in the Disk Target tab (Max Disk Size field).
- Solaris: Fixed segmentation fault when having multiple swap devices.
IOMeter is de facto an industry standard for measures of performance.
There is good writeup on how to use IOMeter on VMware communities here. There I'd like also to point out interesting fact that depending of the physical CPU utilization, the results might (or might not) be accurate:
The likelihood of measurement error increases as the server's load increases. Generally servers that are using less than 30% of their available CPU resources can be trusted. In the event that a large VM on a small server is driving all CPUs to high utilization, Iometer results may suffer from some inaccuracy.
The latest IOMeter utility can be downloaded from this link: https://www.iometer.org/doc/downloads.html
