Measuring Storage and IOPS Performance (Windows, Linux, vCenter)

November 15, 2023


Storage performance and IOPS are crucial metrics for analyzing system operations. Measuring and analyzing these parameters can ensure a responsive system operation. Depending on your environment, there are different ways to measure storage and IOPS performance.

This article covers the steps and examples of measuring storage and IOPS performance on Windows, Linux, and vCenter.

Measuring Storage and IOPS Performance


Understanding Storage and IOPS Performance

Storage performance measures the speed and efficiency of read and write operations on storage devices. It encompasses several different metrics to determine storage efficiency. The metrics are a crucial factor that tells how fast applications respond and how quickly data is retrieved and stored.

Among many different parameters, IOPS (Input/Output Operations Per Second) is a vital metric for measuring storage performance. The value measures the total number of the read and write operations a storage handles in one second. IOPS directly affects the responsiveness of applications and services.

Many factors affect IOPS performance, and it's critical to understand everything that influences these values. Elements that impact IOPS measurements include:

  • Hardware. The underlying infrastructure hardware plays a significant role in IOPS performance. This includes the storage device type (HDD, SSD), CPU, and memory type.
  • File systems and software. File system choice and software configurations impact how data is accessed and stored.
  • Workload. The type of workload drastically changes IOPS performance. Different application types, data access mechanisms, and the number of read and write operations differ between workloads.

Therefore, the specific IOPS values differ between computing environments due to element variations.

Measuring Storage and IOPS Performance on Windows

The following steps outline how to measure IOPS performance on a Windows server:

1. In the Start menu, search for Performance Monitor and open the application.

Start Performance Monitor program

2. In the left menu, expand Data Collector Set. Right-click User Defined and choose New->Data Collector Set.

New data collector set

The Data Collector Set wizard starts.

3. Enter a descriptive set name. Choose Create manually (Advanced) and click Next to proceed.

Data collector set name

4. Tick the Performance Counter checkbox and click Next.

Data collector set performance counter

5. Click Add to open the performance counters list.

Add performance counters to data collector set

6. Choose performance counters to log. To monitor disk usage, locate and expand the PhysicalDisk list. Locate each of the following parameters and click Add >> to add them to the counters list:

  • Avg Disk Bytes/Transfer. Average disk throughput.
  • Avg. Disk Queue Length. Average number of queued read/write requests.
  • Avg. Disk Sec./Transfer. Time required for one read/write operation.
  • Disk Bytes/sec. Total disk throughput per second.
  • Disk Transfers/sec. Number of read/write operations per second (IOPS).
  • Split IO/sec. Number of split operations per second (disk fragmentation indicator).
Added counters list for a data collector set

Click OK to confirm the selection.

7. Choose a Sample interval. The sample interval measures each of the counters at the specified interval.

Sample interval data collector set

Click Next to proceed.  

8. Select the root directory. The performance monitor saves the data to the specified location. Click Next to continue.

9. Choose the user account to run the data collector set. Use an account with administrator privileges.

On the same page, select Start this data collector set now to start collecting data immediately. Alternatively, pick Save and close and run the collector during peak hours.

Finish data collector set creation

Click Finish to complete the data collector set creation.

10. The data collector set shows as Running.

Performance monitor running

If you picked the save and close option during creation, right-click the set and choose Start.

11. The collector runs until terminated. To stop the collection and view the data, right-click the collector set and choose Stop.

Stop performance monitor

The action generates an output report. The report saves to the location provided during collector set creation.

12. To view the report from the Performance Monitor window, open Reports->User Defined->[Set name]->[Report name].

Storage performance monitor report

The graph and data are shown in the right panel. Selecting a parameter shows the exact values, including the average, minimum, and maximum values over the measurement period.

Measuring Storage and IOPS Performance on Linux

Linux provides several tools to monitor storage and IOPS performance. The steps below showcase how to use the iostat command to view and collect IOPS performance data:

1. The iostat command is part of the sysstat package. To install it, run:

sudo apt install sysstat

Wait for the installation to complete.

2. Check the disk name using the lsblk command:

lsblk | grep disk
lsblk command disk name terminal output

The first column shows the disk name. Save the name for the following commands.

3. To see how the command works, run the following:

iostat -d -k 1 1 [disk name]
iostat kb read and write per second terminal output

The -d parameter shows the device utilization report, while the -k parameter displays statistics in kilobytes per second. The numbers indicate the time interval in seconds and the number of samples to collect (in this case, one second and sample).

The output shows various disk metrics for the provided device. The kb_read/s and kb_wrtn/s columns are necessary to calculate IOPS.

4. Extract the columns using the awk command:

iostat -d -k 1 1 [disk name] | awk '/[disk name]/ {print "Read: " $(NF-5) ", Write: " $(NF-4)}'
iostat read write extracted awk terminal output

The $NF parameter helps access the final column and counts backward to fetch the correct information.

5. To calculate the average read and write operations over multiple samples, use the following example command and provide the number of samples and disk name:

iostat -d -k 1 [samples] [disk name] | awk '/[disk name]/ {read+=$(NF-5); write+=$(NF-4)} END {print "Read Avg: " read/[samples] ", Write Avg: " write/[samples]}'
iostat five minutes read write average terminal output

The command collects the samples every second and finds the average over the collection. For example, setting samples to 300 collects one sample per second over 300 seconds (five minutes).

Measuring Storage and IOPS Performance on vCenter

If you're using a virtualized workload through VMware vSphere, you need access to the vCenter to monitor the IOPS performance.

The steps below demonstrate how to install VMware PowerCLI and run a PowerShell script that collects and shows IOPS data for each disk per VM:

1. Open PowerShell as an administrator.

2. Install the PowerCLI module with the following command:

Install-Module VMware.PowerCLI -scope CurrentUser
Install-Module VMware.PowerCLI PowerShell output

Press Y to accept the installation and wait for it to complete.

3. Connect to vCenter using the following command:

Connect-VIServer -Server [Server name|IP]

A dialog pops up, prompting you to enter the access information. Provide the username and password for your vCenter account.

4. In case of certificate errors, change the default configuration using the following command:

Set-PowerCliConfiguration -InvalidCertificateAction Ignore -Scope -CurrentUser

5. Save the following script into a .ps1 file:

$metrics = "virtualdisk.numberwriteaveraged.average","virtualdisk.numberreadaveraged.average" 
$start = (Get-Date).AddMinutes(-5)
$report = @()
$vms = Get-VM  | where {$_.PowerState -eq "PoweredOn"}
$stats = Get-Stat -Realtime -Stat $metrics -Entity $vms -Start $start
$interval = $stats[0].IntervalSecs
$hdTab = @{}
foreach($hd in (Get-Harddisk -VM $vms)){
    $controllerKey = $hd.Extensiondata.ControllerKey
    $controller = $hd.Parent.Extensiondata.Config.Hardware.Device | where{$_.Key -eq $controllerKey}
    $hdTab[$hd.Parent.Name + "/scsi" + $controller.BusNumber + ":" + $hd.Extensiondata.UnitNumber] = $hd.FileName.Split(']')[0].TrimStart('['),$hd.CapacityKB}
$report = $stats | Group-Object -Property {$_.Entity.Name},Instance | %{
    New-Object PSObject -Property @{
        VM = $_.Values[0]
        Disk = $_.Values[1]
        DiskSizeKB = $hdTab[$_.Values[0] + "/"+ $_.Values[1]][1]
        IOPSMax = ($_.Group |
            Group-Object -Property Timestamp |
            %{$_.Group[0].Value + $_.Group[1].Value} |
            Measure-Object -Maximum).Maximum / $interval
        Datastore = $hdTab[$_.Values[0] + "/"+ $_.Values[1]][0]

The script collects the average number of read-and-write operations for virtual disks on powered-on VMs over five minutes.

Modify the $start variable to use a different time interval or the $metrics variable to collect different parameters.

6. Run the script with:

./[Script Name].ps1
PowerShell IOPS vCenter script output

The output shows the collected disk IOPS data for all powered-on VMs in the following format:

  • IOPSMax. The maximum IOPS during the specified time interval.
  • Disk. The specific disk instance within the virtual machine.
  • DiskSizeKB. The size of the disk in Kilobytes.
  • Datastore. Name of the data store where the disk is located.
  • VM. Name of the virtual machine.

Note: For VMs or disks with high IOPS, consider switching the storage to an optimized solution.

If you're a phoenixNAP customer, consider changing the VM or disk policy to HPE Alletra All-NVMe. For more info, see our detailed overview of the HPE Alletra All-NVMe storage solution.


This guide showed you several ways to measure storage and IOPS performance. Collect the data during peak hours to see storage performance in critical moments.

Was this article helpful?
Milica Dancuk
Milica Dancuk is a technical writer at phoenixNAP with a passion for programming. With a background in Electrical Engineering and Computing, coupled with her teaching experience, she excels at simplifying complex technical concepts in her writing.
Next you should read
Intel AMX (Advanced Matrix Extensions) Explained
November 2, 2023

This article explores core concepts of the Intel AMX instruction set extension and how it optimizes AI and machine learning tasks.
Read more
8 Best Website Speed and Performance Testing Tools
June 3, 2019

There are programs that answer two of the most common questions web administrators and SEO's keep asking when it comes to server response time: How fast is my...
Read more
MySQL Performance Tuning and Optimization Tips
April 25, 2024

The performance of MySQL databases is an essential factor in the optimal operation of your server. Make sure you are avoiding the common pitfalls concerning MySQL queries and system setup.
Read more
How to Optimize Docker Performance
November 25, 2021

Docker containers tend to outperform other virtualization methods out of the box, but they can be further optimized to offer even better performance. This article discusses...
Read more