LH Cluster Volume I/O Performance Test
This test auto-discovers the volumes in the target storage cluster and reports how well each volume handles the I/O requests it receives. In addition, this test reveals the time taken to complete read and write operations on each volume. This way, the test turns the spotlight on volumes that are experiencing a slowdown and also reveals what is causing the slowdown – load-balancing irregularities across volumes or poor I/O processing capability?
Target of the test : A LeftHand SAN Cluster
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each volume on the target storage cluster.
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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
I/O read rate |
Indicates the rate at which read I/O operations were performed on this volume during the last measurement period. |
Operations/sec |
Ideally, the value of this measure should be high. A steady dip in this measure value could indicate a potential reading bottleneck. |
I/O write rate |
Indicates the rate at which write I/O operations were performed on this volume during the last measurement period. |
Operations/sec |
|
Total I/O |
Indicates the total read and write I/O operations performed on this volume during the last measurement period. |
Operations/sec |
This measure serves as a good indicator of the I/O processing ability of the volume. 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 this volume. |
MB/sec |
Comparing the value of these measures across the volumes will clearly indicate which volume 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 volumes. |
Data write rate |
Indicates the rate at which data was written to this volume. |
MB/sec |
|
Data processed |
Indicates the overall rate at which data was read from and written to this volume. |
MB/sec |
|
Pending read operations |
Indicates the rate at which read I/O operations were pending on this volume during the last measurement period. |
Operations/sec |
|
Pending write operations |
Indicates the rate at which write operations were pending on this volume 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 this volume during the last measurement period. |
Operations/sec |
|
Read latency |
Indicates the time taken to complete the read I/O operations on this volume. |
Millisec |
|
Write latency |
Indicates the time taken to complete the write I/O operations on this volume. |
Millisec |
|
Read Cache hits |
Indicates the rate which read operations were serviced from the cache of this volume. |
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. |