EMC ECS VDC Transaction Workload Test

Any read or write operation in ECS is performed in several steps, starting with read or write request being received by any node, to the point when data is server to the client for read operation or acknowledgment is sent to the client for write operation. All of these steps are collectively called a transaction.

The purpose of this test is to collect metrics that will provide insights into the performance of VDC in terms of transactions. Looking at key metrics like Transaction Latency, administrators can understand who much time it is taking from receiving the request and serving data to the client. If at any given point of time administrators finds out that this number is out of the limit, she can further investigate and take corrective actions.

Target of the test : A Dell EMC Elastic Cloud Storage System

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each VDC

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed .
Host	The host for which the test is to be configured. Since the storage device is managed using the IP address of its storage controller, the same will be displayed as host.
Port	The port number at which the specified host listens. By default, this is NULL.
ECS REST API Port	This is the port at which REST API connectivity is provided. By default, port 4443 is used.
Username and Password	To collect performance metrics from the target storage device, the eG agent should be configured with the credentials of a user who is vested with "read-only" privileges to access REST API of the target storage device. Specify the credentials of such a user in the Username and Password text boxes.
Confirm Password	Confirm the password by retyping it here.
Timeout Seconds	Specify the time duration for which this test should wait for a response from the storage system in the Timeout text box. By default, this is 60 seconds.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Read transaction	Indicates the number of reading transactions VDC can support in a second.	Transactions/Sec
Write transaction	Indicates the number of write transactions VDC can support in a second.	Transactions/Sec
Transaction read bandwidth	Indicates the data bandwidth for read transactions supported by VDC per second.	MB/Sec
Transaction write bandwidth	Indicates the data bandwidth for write transactions supported by VDC per second.	MB/Sec
Transaction read latency	Indicates the average latency for reads in milliseconds. Read latency value is calculated as time to the first byte. Latency value indicates the request processing time on the node, it does not include data transfer.	Milliseconds
Transaction write latency	Indicates the average latency for writes in milliseconds. Write latency value is calculated as the time from the last byte to the transaction complete. Latency value indicates the request processing time on the node, it does not include data transfer.	Milliseconds
Total requests	Total number of requests received during the measurement period.	Number
Total successful requests	Total number of requests successfully served during the measurement period.	Number
Total user errors	Total number of user errors during the measurement period.	Number	The detailed diagnosis of this measure provides additional details including Category, Error Type, Error count and Error rate.
Total system errors	Total number of system errors during the measurement period.	Number	The detailed diagnosis of this measure provides additional details including Category, Error Type, Error count and Error rate.
Successful requests	Total successful requests in percentage against total requests received.	Percentage
User errors	Total user errors in percentage against total errors received.	Percentage
System errors	Total system errors in percentage against total errors received.	Percentage