Thanks for the welcome to xtreme and for the kind comment about the hIOmon software.
The hIOmon software does have many features, which are meant to address the wide variety of questions and scenarios that can arise when probing deeper (i.e., "peeling the onion") becomes necessary as an investigation/analysis unfolds.
Anyway, regarding your first question, the short answer is that the hIOmon software can capture TRIM commands from the OS perspective (i.e, the former in your second question above). This is in line with a primary design goal of the hIOmon software: to capture a comprehensive set of I/O operation and performance metrics from the perspective of applications/processes and the OS (in contrast to the device perspective, i.e., as seen by the actual device "at the other end of the cable").
More specifically to your question, the hIOmon software can be configured to capture I/O operation metrics for "control" I/O operations (specifically "Device Control" I/O operations) that specify "Manage Data Set Attributes (MDSA)" requests. These MDSA requests include "TRIM" action requests.
These MDSA "TRIM" action requests are generally issued by the file system related components of the operating system. The hIOmon software can capture the issuance of "TRIM commands" at either the physical volume and/or physical device level within the Windows operating system (the latter is similar to the "PhysicalDisk" level shown within the Windows Performance/System Monitor) regardless of the source.
Additional details about the TRIM command support provided by the hIOmon software can be viewed within the "Background Information" section here:
http://www.hyperIO.com/hIOmon/AddOns...GadgetHelp.htm





What is being monitored on the TRIM command? Is it recording when the OS sends the command signal or is it when the SSD actually deals with the command?
Reply With Quote
Bookmarks