|
h |
IO |
mon |
™ |
||
|
The File I/O Performance Monitor |
|||||
| Making data performSM |
Home | Products & Services | Contact | About hyperI/Osm |
|
Big Picture |
Five Storage Performance Questions |
||
|
When dealing with disk I/O performance concerns and issues, there can often be numerous details and metrics that may need to be assessed. But for starters, it can be prudent to consider the following five basic questions, which also reflect several scenarios for which hIOmon can help provide key I/O operation metrics based upon your own particular computer system environment -- and using your very own actual applications and files as you normally do! |
|||
|
1: What is the maximum I/O operation queue length? At WHEN did this maximum occur? |
|||
|
Having a large number of I/O operations queued at a device can often entails increased response times (i.e., longer waits for the I/O operations to be completed). hIOmon can automatically keep track of the maximum number of queued I/O operations that it observes (for read and write I/O operations separately and combined) and can provide the associated "maximum queue length" metrics not only upon an individual device basis but also for individual files and processes/applications. Moreover, hIOmon can even provide you with a time stamp reflecting exactly when the "maximum queue length" metric value was detected. This can help complete the overall picture by telling you both the what and when of the maximum queue length values! The following screen shot illustrates the use of the hIOmon WMI Browser to display the maximum queue length metric values (which were captured during "Boot Logging" by hIOmon) upon an individual device basis. |
|||
![]() |
| Back to top | |||
|
2: To what extent are I/O operations actually going down to the devices? |
|||
|
You may very well be surprised as to how many of your file I/O operations are (or are not!) satisfied by the system file cache and do not require actual device I/O operations. Obviously, file I/O operations can be satisfied by the system file cache within a fraction of the time usually required by actual device I/O operations, and so can have a tremendous impact upon the overall I/O performance seen by the application. hIOmon can collect an extensive set of system file cache metrics not only upon an individual file basis, but also collectively upon an individual device and process/application basis. These system file cache metrics together with the "Physical Device Extended Metrics" (both uniquely collected by hIOmon) can provide you with important insights as to the actual device usage and I/O performance characteristics of your particular applications. Moreover, hIOmon additionally collects a variety of random/sequential access metrics along with "Fast I/O operation" metrics (which reflect I/O operations that completed within less than a millisecond as observed by hIOmon) to further help you quickly and easily determine the types of I/O operations actually performed at both the file-level and also at the "physical device" level within the operating system. The following screen shot illustrates the use of the hIOmon WMI Browser to display the system file cache "read hit" percentage for the devices (both logical and physical) being monitored by hIOmon. Note that similar displays are available for both files and processes/applications. |
|||
| |||