Hybrid Trim Performance Test (LOGO)
This test evaluates the performance of the Trim command for SATA drives that supports the Hybrid Information feature set.
Test details
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 180 |
Category | Benchmark |
Timeout (in minutes) | 10800 |
Requires reboot | false |
Requires special configuration | false |
Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Running the test
Before you run the test, complete the test setup as described in the test requirements: Hard Disk Drive Testing Prerequisites.
The drive must support the Trim command. The IDENTIFY DEVICE data word 169 bit 0 must set to one (see ACS-2 section 7.18.7.71). The test will send down Trim commands using DATA SET MANAGEMENT command.
Ensure that there is a separate drive available to be used as a logger drive. The test will automatically pick the logging drive. It is important to minimize the amount of activity occurring on the drive outside of the logo test. Since this is a performance test, outside activity may affect the results.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
Check WTT Trace
View Task Log of Run Trim Performance Test.
Open the log file TrimPerf.wtl.
Check for messages that may solve the issue.
Copy the .wtl log file. This is the WTT trace described in the WTT Trace section.
No metrics found
The test depends on Storport ETW tracing being enabled in order to get the command completion metrics. See the ETW Trace section for more information about enabling this tracing.
Ensure no other Storport ETW traces are currently logging. Only one Storport ETW trace can be active at a time.
If you get the error message "The test drive does not support trim", try the following:
Ensure that the SATA SSD's IDENTIFY DEVICE data word 169 bit 0 is set to one.
Try to send a Trim command via DATA SET MANAGEMENT.
Run the test again.
If the test failed because the read and write maximum latency exceeded 500 milliseconds, try the following:
Check the IO latency without Trim. Try to lower the latency below 500 milliseconds.
Check the IO latency with presence of Trim. Try to lower the latency below 500 milliseconds.
For troubleshooting information, see Troubleshooting Device.Storage Testing.
More information
This is simply a wrapper around the normal Trim Performance Test. The only difference is that every I/O the test sends down is with a priority. In addition, the test will only operate on the first couple of GB equal to the cache size of the device.
Test metrics
Command | Metric |
---|---|
Trim |
All TRIM commands must be completed in less than 500 milliseconds. |
IO (with Trim sending at same time) |
|
Use the following steps to manually reproduce this test:
Navigate to the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_[name of drive under test]\[device instance path]\Device Parameters
Right-click Storport, point to New, and then click DWORD (32-bit) Value.
Name the key EnableLogoETW and set the value to 1.
Unplug and then plug the drive under test into the system or reboot the system to enable the registry setting.
Copy the TrimPerf.exe, EtwProcessor.dll, Wex.Common.dll, and Wex.Communication.dll files locally.
Run the command.
Command syntax
Command | Description |
---|---|
TrimPerf.exe /DriveNumber [StorageDriveNumber] /LogDriveLetter [LoggerDriveLetter]: /DeviceType [DeviceType] /Scenario [Scenario] /DiskSize [DiskSize] /Cooldown [Cooldown] |
Runs the test. |
Parameters
Parameter name | Parameter description |
---|---|
WDKDeviceID | Instance path of device to test |
LLU_NetAccessOnly | User account for accessing test file share. |
LLU_LclAdminUsr | User account for running the test. |
StorageDriveNumber | Drive number of device to test |
Verbosity | Verbosity of log output. 0 is least verbose, 4 is most verbose |
DeviceTag | Device tag |
DeviceID | Device number |
IOOperation | Read or Write |
DiskSize | Disk size |
LogFile | Log file name |