OK I know technically what IOPS are. The technical definition is great but I'm not understanding the broader implications. My knowledge is basically:
- IOPS are the input and output operations an application makes
- There are HD IOPS, ram IOPS, network IOPS, etc.
- IOPS can be sequential or random (on average for a specific application)
- Sequential IOPS are good, random IOPS are bad.
But that's about the depth of my understanding. So when someone asks "Does the application you are developing have high or low IOPS count?" I don't know what that entails. The application is web based, so does that mean I need to count the IOPS of IIS or just the IOPS my web app makes? There isn't a lot of file level IO going on, but there is a lot of database traffic. Is "average" based on a single session, all sessions over a day, all days over a week, etc. How can I tell if my database accesses are high or low? What is high and what is low for that matter? How can I tell is they are sequential or random?
And once I figure out all that out and understand what it all means, how do I make it better? How can you lower the IOPS or change it from random to sequential? Or should I even worry or bother with such things? Are there tools to measure this stuff? How can I see what my database IOPS are for example?