Disk Stress

# Purpose: The test should reach the bandwidth limit of the test device for the given test system configuration. 

6 scenarios on all of the found devices, each scenario is run for 15 minutes:

1. Sequential read 
2. Sequential write 
3. Sequential verify (write followed by read and comparison) 
4. Random read 
5. Random write 
6. Random verify

#Any write scenarios (including verify) are skipped for optical devices.

The size of the individual data transfers is is 32 KB.

The test tries to do raw writes, bypassing any file system that is mounted on the hard disk if it can. The test attempts raw writes if one of the following occurs:

• The test can find a raw, unpartitioned disk. 
• The test can find a raw, unformatted volume. 
• The test can find a volume that it can dismount.

If none of the preceding situations are available, the test performs I/O through the file system.

#所以測試時用未分割磁區或是未格式化過的HDD較好

If you are testing any drive that requires media or testing in system-mode on a computer that contains drives that require media, you must insert media into the drives. The media that is used must be formatted and contain data that occupies at least 50% of the media's capacity.

#系統上若有光碟機，需放入資料光碟片，並且光碟容量需使用超過50%。

To ensure best device performance, you should delete any unnecessary files from the test device and should cleanly format or defragment the device before running the test.

#透過測Performance的方式達到Disk stress的目的？

Log File:DiskIO.wtl

Supported operating systems:

• Windows 7 
• Windows Server 2008 R2 
• Windows Vista 
• Windows Server 2003 
• Windows XP 

Command Syntax

	Command option		Description
/a		Run on all associated devices.
/b <blockSize>		Block size (integer) in bytes of IO transactions. MB & KB supported. ex: /b 32KB
/c <scenarios>		Scenarios to test. <scenarios> should be a list delimited with ','s or ';'s. Valid characters are: s: sequential scenario, x: random scenario, r: read access, w: write access, v: verify (writes followed by reads and data verification), ex: /c sv;xr;xw, ex: /c sv,xr,xw
/d <device>		Device identifiers of devices to test delimited with ','s or ';'s. If none are specified all disks are tested. Identifiers include: Instance path, PhysicalDriveX, and Drive letter. An identifier of "any" will cause the test to run on any device on the system. ex: /d "IDE\DISKMAXTOR_6L160M0__________________________BANC1G10\5&2A36C317&0&0.1.0" /d PhysicalDrive1;G:;"PCI\VEN_8086&DEV_2651&SUBSYS_01791028&REV_03\3&172E68DD&0&FA"
/f		Force file mode. The test won't attempt to dismount volumes. This should not be used as an accurate measure of disk performance.
/i <iterations>		Iterations (integer) to run. Cannot be specified with /d. Default is 1 if /d is not specified.
/l <numBuckets>		Number of buckets to use for approximate latency measurements.
/o		Enable testing of optical drives.
/q <queueDepth>		Depth of the IO queue (integer).
/s <size>		Size (integer) in bytes of one iteration. KB, MB, & GB supported. ex: /s 6GB
/t <time>		Time (integer) in seconds to execute. Cannot be specified with /i. You may also use TimeSpan formatting: dd.hh:mm:ss
/v		Use verbose logging /x <file.xml> Name of XML File to use for reporting. If file.xml is undefined a unique name based on machine, date, and time will be used.

Reference:
msdn.microsoft.com