|
Measures reported by HanaSQLWrkLdTest
A key step in identifying the source of poor performance is understanding how much time SAP HANA spends on query execution. By analyzing SQL statements and calculating their response times, you can better understand how the statements affect application and system performance. HANA SQL Workload Test helps administrators to drill down to the potential root-cause of a long running procedure and proceed to optimize them to enhance SAP HANA database performance.
At configured intervals, this test reports the maximum of average time for statement execution and and maximum cursor duration. In addition this test also reports the maximum preparation time and memory size for executing this statement. Using the detailed diagnostics of this test, administrators can figure out the response times and status of the SQL statements and attempt to fine-tune them in order to improve their performance, and consequently, enhance server performance.
Outputs of the test: One set of results for the target database server being monitored
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| AvgExecutionTime |
Indicates the maximum of the average time for statement execution. |
Seconds |
If Execution time is much higher than expected (that can be based on the statement complexity and the number of processed rows), the SQL statement has to be checked more in detail on technical layer to understand the reasons for the high runtime.
Use the detailed diagnosis of this measure to view the Host name, Port number, Client Host, Client ID, Client type, Current statement ID, Start time, System time, Statement status, Last executed time, Last action time, Average execution time, Average cursor duration, Average execution memory size, Average preparation time, and Statement String.
|
| AvgCursorDuration |
Indicates the maximum time for statement execution including communication time with clients. |
Seconds |
If the value for Cursor duration is very high and at the same time significantly higher than the value for Execution time, you have to check which processing steps are executed on the application side between the individual fetches. A high value for Cursor duration can negatively impact the database in general because open changes may impact the MVCC mechanism.
Use the detailed diagnosis of this measure to view the Host name, Port number, Client Host, Client ID, Client type, Current statement ID, Start time, System time, Statement status, Last executed time, Last action time, Average execution time, Average cursor duration, Average execution memory size, Average preparation time, and Statement String.
|
| AvgExecutionMemorySize |
Indicates the maximum memory size used during each execution. |
GB |
Use the detailed diagnosis of this measure to view the Host name, Port number, Client Host, Client ID, Client type, Current statement ID, Start time, System time, Statement status, Last executed time, Last action time, Average execution time, Average cursor duration, Average execution memory size, Average preparation time, and Statement String.
|
| AvgExecPreparationTime |
Indicates the maximum time for statement preparation. |
Seconds |
If the value for Preparation time is responsible for a significant part of the Execution time value you have to focus on optimizing the parsing (for example, sufficient SQL plan cache size, reuse of already parsed SQL statements).
Use the detailed diagnosis of this measure to view the Host name, Port number, Client Host, Client ID, Client type, Current statement ID, Start time, System time, Statement status, Last executed time, Last action time, Average execution time, Average cursor duration, Average execution memory size, Average preparation time, and Statement String.
|
|