View TPV summary reports

View TPV summary reports

+
Search Tips | Advanced Search

Overview

The Tivoli Performance Viewer (TPV) provides five different summary reports that make important data quickly and easily accessible. View summary reports to help you find performance bottlenecks in your applications and modules.
This article assumes that one or more applications or modules are deployed and running on one or more servers.
We can view TPV summary reports on the following:

Servlets The servlet summary lists all servlets that are running in the current application server. Use the servlet summary view to quickly find the most time intensive servlets and the applications that use them, and to determine which servlets are invoked most often. We can sort the summary table by any of the columns.

Sort by Avg Response Time to find the slowest servlet or JavaServer page (JSP).
Sort by Total Requests to find the servlet or JSP used the most.
Sort by Total Time to find the most costly servlet or JSP.

Enterprise beans The EJB summary lists all enterprise beans running in the server, the amount of time spent in their methods, the number of EJB invocations, and the total time spent in each enterprise bean
total_time = number_of_invocations * time_in_methods
Sort the various columns to find the most expensive enterprise bean. Also, if the PMI counters are enabled for individual EJB methods, there is a check box next to the EJB name that one can select to see statistics for each of the methods.

Sort by Avg Response Time to find the slowest enterprise beam.
Sort by Method Calls to find the enterprise bean used the most.
Sort by Total Time to find the most costly enterprise bean.

EJB methods The EJB method summary shows statistics for each EJB method. Use the EJB method summary to find the most costly methods of your enterprise beans.

Sort by Avg Response Time to find the slowest EJB method.
Sort by Method Calls to find the EJB method used the most.
Sort by Total Time to find the most costly EJB method.

Connection pools The connection pool summary lists all data source connections that are defined in the application server and shows their usage over time.
When the application is experiencing normal to heavy usage, the pools used by that application should be nearly fully utilized. Low utilization means that resources are being wasted by maintaining connections or threads that are never used. Consider the order in which work progresses through the various pools. If the resources near the end of the pipeline are under utilized, it might mean that resources near the front are constrained or that more resources than necessary are allocated near the end of the pipeline.
Thread pools The thread pool summary shows the usage of all thread pools in the application server over time.
When the application is experiencing normal to heavy usage, the pools used by that application should be nearly fully utilized. Low utilization means that resources are being wasted by maintaining connections or threads that are never used. Consider the order in which work progresses through the various pools. If the resources near the end of the pipeline are under utilized, it might mean that resources near the front are constrained or that more resources than necessary are allocated near the end of the pipeline.

The default monitoring level enables all reports except the report on EJB methods. To enable the EJB method summary report, configure PMI to use a set of statistics that includes EJB method metrics (All or Custom).
You view TPV summary reports in the administrative console.

Procedure

Click...
Monitoring and Tuning | Performance Viewer | Current Activity | servername | Summary Reports

...in the console navigation tree.
Select the code artifact or pool for which you want a summary report. Expand the Summary Reports node of the TPV navigation tree on the left side of the Tivoli Performance Viewer page to see links for the types of summary reports. After clicking on a link for an artifact or pool, a list of artifacts or pools on the server is displayed on the right side of the page.
Select the artifact or pool for which you want to view a summary report.

Related Tasks
Configuring TPV settings
Monitoring performance with Tivoli Performance Viewer (TPV)

See Also
Using the Tivoli Performance Viewer

Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.

Servlets	The servlet summary lists all servlets that are running in the current application server. Use the servlet summary view to quickly find the most time intensive servlets and the applications that use them, and to determine which servlets are invoked most often. We can sort the summary table by any of the columns. Sort by Avg Response Time to find the slowest servlet or JavaServer page (JSP). Sort by Total Requests to find the servlet or JSP used the most. Sort by Total Time to find the most costly servlet or JSP.
Enterprise beans	The EJB summary lists all enterprise beans running in the server, the amount of time spent in their methods, the number of EJB invocations, and the total time spent in each enterprise bean total_time = number_of_invocations * time_in_methods Sort the various columns to find the most expensive enterprise bean. Also, if the PMI counters are enabled for individual EJB methods, there is a check box next to the EJB name that one can select to see statistics for each of the methods. Sort by Avg Response Time to find the slowest enterprise beam. Sort by Method Calls to find the enterprise bean used the most. Sort by Total Time to find the most costly enterprise bean.
EJB methods	The EJB method summary shows statistics for each EJB method. Use the EJB method summary to find the most costly methods of your enterprise beans. Sort by Avg Response Time to find the slowest EJB method. Sort by Method Calls to find the EJB method used the most. Sort by Total Time to find the most costly EJB method.
Connection pools	The connection pool summary lists all data source connections that are defined in the application server and shows their usage over time. When the application is experiencing normal to heavy usage, the pools used by that application should be nearly fully utilized. Low utilization means that resources are being wasted by maintaining connections or threads that are never used. Consider the order in which work progresses through the various pools. If the resources near the end of the pipeline are under utilized, it might mean that resources near the front are constrained or that more resources than necessary are allocated near the end of the pipeline.
Thread pools	The thread pool summary shows the usage of all thread pools in the application server over time. When the application is experiencing normal to heavy usage, the pools used by that application should be nearly fully utilized. Low utilization means that resources are being wasted by maintaining connections or threads that are never used. Consider the order in which work progresses through the various pools. If the resources near the end of the pipeline are under utilized, it might mean that resources near the front are constrained or that more resources than necessary are allocated near the end of the pipeline.