eG Monitoring
 

Measures reported by PureArrPerfTest

Using this test, administrators can figure out how well the FlashArray processes the I/O requests and detect delay encountered during processing the I/O requests. In addition, this test also reports the data utilization for performing read/write operations on the FlashArray. Using the metrics reported by this test, administrators can take remedial measures to keep a check on the irregularities, if any.

Outputs of the test : One set of results for the target FlashArray being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
readBandwidth Indicates the amount of data utilized for performing read operations on this FlashArray per second. MB/Sec A consistent decrease in the value of these measures indicates an I/O processing bottleneck.
writeBandwidth Indicates the amount of data utilized for performing write operations on this FlashArray per second. MB/Sec
avgBandwidth Indicates the average amount of data utilized for performing I/O operations on this FlashArray per second. MB/Sec  
readOps Indicates the number of read operations performed on this FlashArray per second. IOPS A consistent decrease in the value of these measures indicates an I/O processing bottleneck.
writeOps Indicates the number of write operations performed on this FlashArray per second. IOPS
avgIOPS Indicates the average number of I/O operations performed on this FlashArray per second. IOPS  
readLatency Indicates the time taken to process the read operations during the last measurement period. Milliseconds Very high values for these measures are indicative of the existence of road-blocks to rapid reading/writing by the FlashArray.
writeLatency Indicates the time taken to process the write operations during the last measurement period. Milliseconds
avgLatency Indicates the average time taken to process the I/O operations during the last measurement period. Milliseconds Ideally, the value of this measure should be very low. A high value or a steady increase in this value could indicate an I/O processing bottleneck on the array. In such a case, compare the value of the readLatency and writeLatency measures to figure out where the slowness is worst - when processing read requests? or write requests?
depth Indicates the number of IO requests in the queue. Number A consistent increase in this value indicates a potential processing bottleneck with the FlashArray.