Fairly often I find myself writing tools to accomplish a specific task that make use of only a subset of the potential resources available in a toolchain. When I have what I need, I basically toss the code away if I don't have time to complete it, since I think that a partial solution is useless.
This attitude is completely wrong, but I still succumb to it consistently. Even a partially complete output parser is still more complete than what I had when I started, for instance.
In an effort to rid myself of this habit, I'll be posting some of the various tools that I've written for various purposes. The inaugural piece is an IOMeter output parser.
Next week's InfoWorld will feature an exhaustive (and certainly exhausting) roundup of iSCSI SAN arrays. I performed I/O testing on each array from Windows and Linux using IOMeter, but found the output handlers included with the package lacking in many ways. The Microsoft Access importing tool, wizard.mdb, simply wouldn't function on any Office version I tried, rendering all other tools stemming from that one useless. I didn't need Access anyway -- that's like taking Greyhound to the grocery store. All I needed was to have the output CSV files parsed into a relatively readable format.
So I wrote two, in Perl. The first is a text-only version that runs in a directory containing IOMeter CSV output files, one target per file, and displays the results in a more-or-less formatted way. The second performs the same function, but outputs HTML for easier digestion.
In keeping with my "incomplete, therefore useless" motivation, these tools don't parse every IOMeter output datapoint, and only display IOps, MBps, CPU utilization, and a few read/write splits. If you want more, work with the code.
I figure that more than a few folks could use these as a starting point, at least. Have at 'em.