P6 EPPM Connection Pool Performance Test
THe Oracle Primavera P6 EPPM Server allows connections to many different clients including Desktop clients, API clients, Webservice clients and other reporting clients. EPPM manages client connections using connection pools which create, allocate and terminate connections as and when required. It is quite useful for administrators for administrators to keep an eye on availability of connections in connections pools, so as to ensure that unused connections are free up and new connections are allocated whenever a new client comes to join.
This test monitors the connection pools and provide important insights about connection performance, availability, waiting time and query performance over these connections.
Target of the test : An Oracle Primavera P6 EPPM Server
Agent deploying the test : An internal/external agent
Outputs of the test : One set of results for each connection pool hosted on P6 EPPM Server
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. |
JMX Remote Port |
Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application |
JMX UserName and JMX Password |
If JMX requires authentication only (but no security), then ensure that the User and Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to the |
Confirm Password |
Confirm the password by retyping it here. |
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:
|
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Average SQL time |
Indicates the average time taken to execute SQL queries. |
Seconds |
If this time is increasing over repeated measurements, it is cause of concern. |
Average lease time |
Indicates the average time a user holds the connection. |
Seconds |
Administrators can use this metrics to plan the capacity required for the system. |
Average lease wait time |
Indicates the average time a users has to wait to acquire the connection. |
Seconds |
If this time is increasing over repeated measurements, it is cause of concern. |
Connections allocated |
Indicates the number of connections made available and allocated to the users during last measurement period. |
Number |
|
Connections in use |
Indicates the number of leased connection that are involved in database transactions. |
Number |
Very high number of connections in use can degrade the system performance so administrators need to investigate if number of active connection stays high for longer period of time. |
Percentage of connection usage |
Indicates the number of connection which are in use against the total number of leased connections. |
Percentage |
Number of connection used should be optimal, it shouldn't be too low , which would mean capacity is not fully utilized. Also, it should not be too high which means it will not be possible to allocate new connections. |
Waiting for lease |
Indicates the number of users who are waiting for the connection to be made available and acquire it. |
Number |
If this metrics is high, it means more users want to connect to system than capacity. |
Connections leased |
Indicates the number of connections that have been reserved by active user transactions. |
Number |
|
Connections recycled |
Indicates the number of previously leased connections which have been forcibly returned to connections pool due to lease timeout while connection was not in use. |
Number |
While it is good to recycle connections but revoking connections in the middle of transaction can cause the user real inconvinience. |
Connections revoked |
Indicates the number of previously leased connections which have been forcibly returned to connections pool due to lease timeout during a database transaction. |
Number |
|
Succeeded lease requests |
Indicates the number of users who were successful in leasing a connection on request. |
Number |
If there are too many denied requests, which means the connection availability is too low. |
Denied lease request |
Indicates the number of database connection lease request which were denied due to the connection pool not having any free connections. |
Number |
|
SQL queries |
Indicates the number of SQL queries executed across the connections. |
Number |
|