Pure Volumes Test

For users to be able to read from/write data into volumes quickly, adequate space must be available in the volumes and the I/O requests should be processed rapidly by the volumes. Slowdowns in data storage/retrieval can be attributed to storage space contentions experienced by one/more volumes or I/O processing bottlenecks. In the event of such slowdowns, administrators need to swiftly isolate the following:

• Which volumes are over-utilized?
• Which volumes are overloaded?
• Which volumes are experiencing serious latencies?
• When were these latencies observed most frequently – while reading or writing?

The Pure Volumes test provides accurate answers to these questions. With the help of these answers, you can quickly diagnose the root-cause of slowdowns when reading from/writing into a volume.

Target of the test : Pure Storage FlashArray

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each volume of the target FlashArray.

Configurable parameters for the test

Parameter	Description
Test Period	How often should the test be executed.
Host	The IP address of the host for which this test is to be configured.
Port	The port at which the device listens. By default, this will be NULL.
API Token	The eG agent collects the required metrics from the Pure Storage Flash Array by executing API commands using Pure Storage REST API on the FlashArray and pulls out critical metrics. In order to collect metrics, the eG agent should be provided with a valid API token. To know how to determine the API token, refer to Pre-requisites for Monitoring the Pure Storage FlashArray. Specify the determined API token in the API Token text box.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Read bandwidth	Indicates the amount of data utilized for performing read operations on this volume per second.	MB/Sec	A consistent decrease in the value of these measures for a volume indicates an I/O processing bottleneck.
Write bandwidth	Indicates the amount of data utilized for performing write operations on this volume per second.	MB/Sec
Average bandwidth	Indicates the average amount of data utilized for performing I/O operations on this volume per second.	MB/Sec	Compare the value of this measure across the volumes to know the volume that uses more bandwidth to process the I/O requests.
Read IOPS	Indicates the number of read operations performed on this host per second.	IOPS	A consistent decrease in the value of these measures for a volume indicates an I/O processing bottleneck.
Write IOPS	Indicates the number of write operations performed on this volume per second.	IOPS
Average IOPS	Indicates the average number of I/O operations performed on this volume per second.	IOPS	This measure is a good indicator of I/O load on every host connected to the FlashArray.
Read latency	Indicates the time taken by this volume 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 on the volumes.
Write latency	Indicates the time taken by this volume to process the write operations during the last measurement period.	Milliseconds
Average latency	Indicates the average time taken by this volume to process the I/O operations during the last measurement period.	Milliseconds	A consistently high value for this measure is a cause of concern.