EMC Centera Utilization Test
For any client or administrator, the performance of the storage system is the primary concern. For performance to be optimal it is imperative that all components within the system are working at high efficiency. To manage system performance and fix any potential issues, administrators needs to keep track of key performance indicators so that they are the first ones to know if there is any performance bottleneck. For EMC Centera storage, Utilization Test can help in this regard.
This test reports the key indicators of efficient performance like throughput, transaction rate, lookup time etc. By closely monitoring these measures, administrators may be alerted to investigate the reasons for the delays, storage issues etc., and resolve the issue before the overall performance of the storage system gets affected.
Target of the test : An EMC Centera storage system.
Agent deploying the test : A remote agent
Outputs of the test : One set of result for target storage system
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port number at which the specified host listens. By default, this is NULL. |
|
User and Password |
In order to monitor an EMC Centera Storage, the eG agent has to be configured with the credentials of a read only user. Specify the login credentials of such a user in the User and Password text boxes. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
CerteraViewer JAR Path |
Path of CenteraViewer on agent host. CenteraViewer is installed along with CenteraCLI. By default the installation path is C:\Program Files\EMC\Centera\2_4\SystemOperator\lib\CenteraViewer.jar |
|
Timeout Seconds |
Specify the time duration (in seconds) beyond which this test should time out in the TIMEOUT text box. The default is 120 seconds. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Average Throughput |
Indicates the rate at which reads and writes are being performed. |
MB/Sec |
If the throughput is on a downward trend over a period of time, it may be an indication of underlying problem which needs to be investigated. |
|
Read Transactions |
Indicates the total read transactions over the last measurement period. |
Number |
This number can be monitored over multiple measurements and if there is a constant downward trend, investigation may be required |
|
Average Read Transactions |
Indicates the total read transactions in a second. |
Number |
This number can be monitored over multiple measurements and if there is a constant downward trend, investigation may be required |
|
Average read size |
Indicates the average size of reads. |
Kb/Transaction |
This number should be looked in conjunction with above measures, if the size of reads is large, the throughput and number of transactions will come down |
|
Read Transactions percentage |
Percentage of read transactions out of total transactions. |
Percentage |
Gives an idea of how the storage is being used |
|
Maximum lookup time |
Indicates the maximum time taken for data object lookup during the measurement period. |
Milliseconds |
|
|
Data reads |
Percentage of read data out of total data. |
|
Gives an idea of how the storage is being used |
|
Average Written |
Average rate at which data is being written to disk. |
MB/Sec |
This measure should be monitored over a period of time to isolate and identify the issue. |
|
Write Transactions |
Total number of write transactions over measurement period. |
Number |
This number can be monitored over multiple measurements and if there is a constant downward trend, investigation may be required |
|
Average write transactions |
Indicates the total write transactions over the last measurement period. |
|
This number can be monitored over multiple measurements and if there is a constant downward trend, investigation may be required |
|
Average write size |
Indicates the average size of writes. |
Kb/Transaction |
This number should be looked in conjunction with above measures, if the size of reads is large, the throughput and number of transactions will come down |
|
Write data |
Percentage of write data out of total data. |
Percentage |
|
|
Write transactions percentage |
Percentage of write transactions out of total transactions. |
Percentage |
|
