Item | Description | Evaluation |
|---|---|---|
Processing time (avg/max/min) | The maximum, minimum and mean processing times for EJB applications. | When the maximum processing time for an entire period (one day) is long and the mean processing time is close to the maximum processing time The following causes are possible: There is a performance-related problem with the server application. The load on the system is high. Review the server applications and the system, giving particular attention to the above factors. When the maximum, minimum and mean processing times within a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum processing time is long but the mean processing time is short and close to the minimum processing time The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors. |
Wait time (avg/max/min) | The maximum, minimum and mean times from when a client receives a request until a method commences processing. | When the maximum, minimum and mean wait times during a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum wait time is long but the mean wait time is short and close to the minimum wait time The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors. When the maximum wait time and the mean wait time are long throughout a performance monitoring period The performance of a server application is not sufficient to handle the number of requests from a client. Take measures to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. |
Number of received requests and the number of process wait requests | The cumulative number of processes that have been handled by the object since performance monitoring began, and the maximum number of requests that had to await processing by the object. | When there are many processes and process wait requests within a specific period The number of requests to a server application within a specific period has increased. If the performance of a server application is not sufficient to handle the number of requests from a client, take measures to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance information of other server applications as well to confirm the load status. When the number of process wait requests is large but the mean wait time is short Use the isinfobj command to regularly check the queue status, and also check the load status during the collection interval. |
Amount of VM memory used | Maximum and mean values of the amount of VM memory used | If a large amount of VM memory is being used, there may be a memory leak. Review the server applications with a view to identifying objects that can be deleted. |
Number of sessions | The number of current EJB objects | If the number of EJB objects becomes larger than the number of connected clients, the "remove" method may not have been issued to the "create" method. Review the client applications. |
