Sybase Engine Test
This test measures the efficiency of the Sybase engines by monitoring the CPU usage of each engine. You will have to enable the enable monitoring configuration parameter to make this test work.
Target of the test : A Sybase ASE server on which the MDA tables have been installed
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every Sybase ASE engine being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
Refers to the IP address of the Sybase ASE server. |
Port |
The port number at which the Sybase server listens to. |
User |
To enable this test to connect to the Sybase server and collect the required metrics, it is enough if you configure the test with the name of a Sybase user who has the “mon_role”. However, for best results, it is recommended that you configure all Sybase tests with the credentials of a Sybase user who has the “mon_role”, “sa_role’, and “sybase_ts_role”. |
Password |
The password corresponding to the above user |
Confirm Password |
Confirm the password by retyping it here. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Percentage CPU busy |
The percentage of CPU used by this engine during the last measurement period, for processing queries. |
Percent |
A high value for this measure indicates excessive utilization of CPU. The CPU utilization may be high because a few queries are consuming a lot of CPU, or because there are too many queries contending for a limited resource. Check the currently running queries to see the exact cause of the problem. If one/more queries appear to be resource-intensive, you might have to fine-tune them to make them resource efficient. |
Percentage system busy |
The percentage of CPU used by this engine during the last measurement period, for system-level processing. |
Percent |
An unusually high value indicates a problem and may be due to too many system-level tasks executing simultaneously. |
Percentage user busy |
The percentage of CPU used by this engine during the last measurement period, for processing user requests. |
Percent |
A high value for this measure indicates that one/more user transactions are consuming too much CPU. You can take the help of the detailed diagnosis information provided by the Avg CPU time measure reported by the Sybase Statement test to identify the user queries that are consuming CPU resources excessively. Once identified, you might have to fine-tune the application that initiated the query. |
Percentage idle |
The percentage of time for which the CPU was idle during the last measurement period. |
Percent |
|