How To Measure Iops On Windows

One of the main metrics, which allows to estimate the performance of the existing or developed storage arrangement isIOPS (Input/Output Operations Per 2d). In simple terms, IOPS is the number of blocks read from or written to a media or a file organisation in a time unit. The larger is this number, the college is the performance of the deejay subsystem. (Bluntly speaking, the IOPS value has to be considered together with other data storage characteristics, like average latency,  throughput, etc.)

Y'all can roughly estimate the performance of a disk subsystem using performance counters inPerformance Monitor (like Disk Reads/sec, Disk Writes/sec, Current Disk Queue Length).

I needed to take a more than visual and user-friendly PowerShell tool at hand, which allowed to quickly measure out the current performance of a data storage system in IOPS, whether they are a local hd, an SSD, a network folder (SMB), a CSV volume or a LUN on the SAN (Storage Area Network ).

I have establish a PowerShell script (by Mikael Nystrom, Microsoft MVP), which is substantially an add-on toSQLIO.exeutility(a gear up of file storage performance tests). Although there is SQL in the proper noun of the utility, MSSQL is not required: it can be used in any Windows system.

Note. In December, 2015, Microsoft appear the end of support for this tool and substitution of SQLIO for a multipurpose utilityDiskspd, and removed SQLIO distribution files from its website. And then yous volition have to expect for sqlio.exe yourself, or download information technology from our website. (Information technology is in the annal with the script.)

So, download the archive containing 2 files:SQLIO.exe andDiskPerformance.ps1 (disk_perf_iops.Aught — 74 KB) and extract information technology to any folder.

Important. When using a script, quite a considerable load is generated on the disks and CPU of the tested system. To eliminate the performance degradation for users, it is not recommended to offset it on productive systems in peak hours.

An example of running a script to estimate IOPS:

.\DiskPerformance.ps1 -TestFileName test.dat –TestFileSizeInGB 1 -TestFilepath C:\temp -TestMode Get-LargeIO -FastMode True -RemoveTestFile True -OutputFormat Out-GridView

Let's consider the script arguments:

-TestFileName examination.dat

The proper name of the file created past FSUTIL

–TestFileSizeInGB 1

The size of the examination file. Possible variants are 1.5, 10, 50, 100, 500, i,000 GB. The file size has to be larger than the size of the organization cache. Otherwise, IOPS will be measured for the cache information, instead for the disk.

-TestFilepath C:\Temp

Hither you specify the disk to approximate the operation for and the folder on the disk, in which a test file will be created. You tin can also specify an UNC path to the shared folder.

-TestMode Get-LargeIO

There are ii variants of input-output measurement:Become-SmallIO allows to measure IOPS, andBecome-LargeIOmeasures data manual rate. The difference between SmallIO and LargeIO arguments is in the cake size of 8 KB and 512 KB while measuring the charge per unit, and the type of access, Random or Sequential, correspondingly.

-FastMode Truthful

In the Fastmode, each test takes ten seconds, otherwise it takes 60 seconds.

-RemoveTestFile True

Remove the test file after the examination is over.

-OutputFormat Out-GridView

The test results tin be displayed either in PowerShell console (Format-Tabular array) or in a separate graphic chart window (Out-Gridview).

In our case (a virtual disk in the VMFS storage on HP MSA 2040 with SAN admission) the disk array showed the average IOPS value of about15,000 and the data transmission rate (throughput) nigh5 Gbit/s.

In the following tabular array, the gauge IOPS values for different disk types are shown:

Type	IOPS
SSD(SLC)	6000
SSD(MLC)	thou
15K RPM	175-200
10K RPM	125-150
7.2K RPM	50-75

I take found some considerations on operation in IOPS for some popular services:

1. Microsoft Exchange 2010with 5,000 users, each of them getting 75 and sending 30 letters a day, requires at least 3,750 IOPS
2. Microsoft SQL 2008 Serverwith 3,500 SQL transactions per second (TPS) requires 28,000 IOPS
3. A mutual Windows application serverfor 10-100 users requires x-40 IOPS

Source: https://virtualtechnoblog.wordpress.com/2016/10/30/how-to-measure-disk-iops-using/

Posted by: lewissatepas64.blogspot.com

Share this post