Use this page to view the performance of the J2EE and Database components of your middle tier in the context of a specific request. The specific request is shown immediately below the page title.
Depending upon the J2EE / database component you selected, this page by default contains a summary of Servlet, JSP, EJB method, or JDBC connections called by the selected request. However, you can switch between views of the components or display a summary of all the component invocations called by the selected request.
This page is part of the Middle-Tier request Performance Monitoring features of Oracle Enterprise Manager. For more information about obtaining a complete, end-to-end view of your application performance, see About Monitoring Middle Tier Performance.
This topic includes the following sections:
General Usage Tips
Reviewing the Servlet, JSP, and EJB Methods Invoked by the request
Reviewing the JDBC Activity for the request
Select from the View Component menu to switch between views of the J2EE and Database component performance data. For example, select JSPs from the menu to display the performance data for all JSPs called by this request, or select JDBC to display performance data for all the JDBC connections called by the request.
Besides showing the percentage of processing time used by each component, the chart on this page also shows the Dispatch Time, which represents the time taken for OC4J container to dispatch requests to the OC4J components.
For each Servlet, JSP, or EJB Method, Enterprise Manager provides metrics that can help you determine how much processing time was consumed by this component for each time a user requested the selected request. This analysis can help you focus on the components that have the most impact on your request performance.
The following table summarizes the Performance page metrics that are common to the Servlet, JSP, and EJB Method subsystem component types.
|
Metric
|
Description
|
|---|---|
| Invocations per Hit | The average number of times the selected J2EE and database component was invoked each time a user requested the request. |
| Component Time Per Hit | The average amount of time spent processing the selected component each time a user requested the request. |
| Time Per Component Invocation | The average time spent processing the selected component each time the component was invoked by the request. |
| % of Request |
The amount of time spent in this call per each request of this request as a percentage of the total request processing time. |
| Average Invocations | The average number of times this call was made (on average) for each request to this request; generally, this will be 1, but if a call is made multiple times or only during certain conditions, the number may be less than or greater than 1. |
| Exclusive to Call (ms) | The time spent in this call exclusive
of any time spent in other calls made from this component call. For example, if this call took a total of 10 seconds and calls made from this took 7 seconds, then the time exclusive to this call is the difference (3 seconds). |
| In Callouts (ms) | The time spent in calls made from this call; In the above example, this would be the 7 seconds. |
| Call Time Breakdown | A graphic representation of the time spent in this call compared to calls made to other components. Click the chart to drill down to examine the invocation details; the invocation details page includes a table of the calls made to other components. |
For each JDBC connection made by the selected request, Enterprise Manager provides information that can help you determine how the average processing time consumed by JDBC connections each time a user requests the selected request. This analysis can help you focus on the JDBC connections and SQL statements that have the most impact on your request performance.
Use this area of the page to first review how many JDBC connections were made and how much time was spent processing those connections, on an average, each time a user requested the request.
Second, use the JDBC connections table to review the load and performance of each individual JDBC connection made by the request. The following table summarizes the metrics available for each JDBC call by the request.
|
Metric
|
Description
|
|---|---|
| Data Source | The J2EE data source to which the JDBC connection is established. |
| Schema | The database schema against which the JDBC connection is established. |
| % of Request |
The amount of time spent in this call per each request of this request as a percentage of the total request processing time. |
| Connects Per Hit | The average number of JDBC connections made each time a user requested the selected request. |
| Connect Time Per Hit | The average time spent making a JDBC connection each time a user requested the selected request. |
| SQL Time Per Hit | The average amount of time spent the executing SQL statements and fetching data each time a user requested the request. Note that this metric is the sum of the SQL execution time and the fetch time. |
Use this area of the page to first review general information about the load and performance of all the SQL statements called by the selected JDBC connections.
Enterprise Manager measures this load and performance by providing both the average number of times SQL statements were executed and the average number of times data was fetched from the data source on behalf of a SQL statement.
Enterprise Manager also measures the amount of time spent executing SQL, as well as the time spent fetching data. Note that the sum of the average SQL Execution Time Per Hit and the average Fetch Time Per Hit is equivalent to the SQL Time Per Hit statistic for the selected JDBC connections in the JDBC Connections table.
To provide even more insight into the performance of your JDBC connections, the component performance page also lists the actual SQL statements called by the selected JDBC connections. Enterprise Manager provides the following statistics for each SQL statement to help you identify the high-impact SQL statements.
|
Metric
|
Description
|
|---|---|
| SQL Statement | The actual SQL statement called by the JDBC connection. Click the statement to display the Invocation Details page for the SQL Statement. |
| Data Source | The J2EE data source against which the SQL statement is executed. |
| Schema | The database schema against which the SQL statement is executed. |
| % of Request |
The amount of time spent in this specific SQL statement per each request of this request as a percentage of the total request processing time. |
| Average Invocations | The average number of times this SQL statement was executed each time the request invoked the JDBC connection. Generally, this will be 1, but if a call to this SQL statement is made multiple times or only during certain conditions, the number may be less than or greater than 1. |
| SQL Execution Time Per Hit | The average amount of time spent executing the SQL statement each time the request invoked the selected JDBC connection. |
Related Topics
About Web Application Management
About Monitoring Middle Tier Performance
Viewing the Entire Middle-Tier Call Stack for a Request
Viewing Middle-Tier Performance Data
Correlating Middle-Tier Request Performance
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.