search cancel

UIM: Monitoring IOPS using ntperf

book

Article ID: 216567

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

How to configure ntperf to monitor IOPS?

Environment

Release : 20.3

Component : UIM - NTPERF

Resolution

Please create a new profile, and then choose PhysicalDisk under the Object. There are counters such as 

  • Disk sec/Transfer – the time required to perform one write/read operation with the storage device or disk (disk latency). If the delay is more than 25 ms (0.25), then the disk array cannot handle the I/O operation on time. For high load servers, the disk latency value should not exceed 10 ms (0.1);
  • Disk Transfers/sec – (IOPS). The number of read/write operations per second. This is the main indicator of the disk access intensity 
  •  Disk Bytes/Sec – Total disk throughput (read+write) per second. Maximum values depend on the disk type (150-250 Mb/s – for a regular HDD disk and 500-10000 for SSD);
  • Split IO/sec – a disk fragmentation indicator when the operating system has to split one I/O operation into multiple disk requests. It may also indicate that the application is requesting too large blocks of data that cannot be transferred in one operation

Based on your need you can monitor one or several of them:

 

Additional Information

Ref:  http://woshub.com/how-to-measure-disk-iops-using-powershell/


Microsoft Exchange 2010 with 5,000 users, each of them receives 75 and sends 30 emails per day, will require at least 3,750 IOPS;

Microsoft SQL 2008 Server with 3,500 SQL transactions per second (TPS) requires 28,000 IOPS;

A common Windows application server for 10-100 users requires 10-40 IOPS

Attachments