LH Cluster I/O Performance Test

This test reports how well the cluster handles the I/O requests it receives. In addition, this test also reveals the time taken by the cluster to complete the read and write operations and the number of I/O operations that are pending on the cluster. This way, the test helps administrators to find out the processing bottleneck (if any) and take remedial actions before the slowness in I/O processing affects the performance of the storage system.

Target of the test : A Lefthand SAN Cluster

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the Storage cluster being monitored.

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 host is listening.
CLI Path	The eG agent uses the command-line interface, CLIQ.exe, to communicate with and monitor the storage cluster. To enable the eG agent to invoke the CLI, configure the full path to the CLI in the CLI Path text box.
Username and Password	Specify the credentials of a user who can execute the CLIQ.exe on the host that is connected with the storage cluster in the Username and Password text boxes.
Confirm Password	Confirm the password by retyping it here.
Timeout	Specify the duration (in seconds) beyond which the test will timeout in the Timeout text box. The default value is 60 seconds.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
I/O read rate	Indicates the rate at which read I/O operations were performed on the cluster during the last measurement period.	Operations/sec
I/O write rate	Indicates the rate at which write I/O operations were performed on the cluster during the last measurement period.	Operations/sec
Total I/O	Indicates the total read and write I/O operations performed on the cluster during the last measurement period.	Operations/sec	This measure serves as a good indicator of the I/O processing ability of the cluster. A consistent drop in this value is hence a cause for concern, as it indicates a processing slowdown.
Data read rate	Indicates the rate at which data was read from the cluster.	MB/sec	Comparing the value of these measures across the clusters will clearly indicate which cluster is the busiest in terms of the rate at which data is read and written - it could also shed light on irregularities in load balancing across the clusters.
Data write rate	Indicates the rate at which data was written to this cluster.	MB/sec
Data processed	Indicates the overall rate at which data was read from and written to the cluster.	MB/sec
Pending read operations	Indicates the rate at which read I/O operations were pending on the cluster during the last measurement period.	Operations/sec
Pending write operations	Indicates the rate at which write operations were pending on the cluster during the last measurement period.	Operations/sec
Pending I/O operations	Indicates the overall rate at which read and write I/O operations were pending on the cluster during the last measurement period.	Operations/sec
Read latency	Indicates the time taken to complete the read I/O operations on the cluster.	Millisec
Write latency	Indicates the time taken to complete the write I/O operations on the cluster.	Millisec
Read Cache hits	Indicates the rate which read operations were serviced from the cache of the cluster.	Operations/sec	Ideally, the value of this measure should be high. A consistent drop in cache hits and a steady increase in cache misses during the same time frame is indicative of ineffective read cache usage, which can lead to a slowness in read request servicing.