Page History
...
The summary area displays the following information for the selected node. The value displayed is the aggregated value for the selected node’s node's underlying call path (unless otherwise stated) in the selected time frame:
- SLA Compliance. Displays the relative percentage of HTTP entry point service requests that approached or breached the defined SLA thresholds.
- Avg. Response Time (Sec). Displays the average response time for the selected node. The average response time is displayed in seconds.
- Executions. Displays the number of executions within the selected node.
- Sum. Response Times. Displays the total response time for the selected node. The summed response time is displayed in hours: minutes: seconds: milliseconds.
- Avg. CPU Time (Sec). Displays the average time that CPU was consumed for the selected node and its underlying call path.
- Method Type (when a method is selected only). Displays the method type.
- Impact on Entry Point (when a method or an SQL is selected only). Displays the percent value of the selected node’s node's summed response time out of its entry point’s summed response time.
- Max. Response Time (Sec) (when an SQL is selected only). Displays the peak response time detected in the selected time frame.
...
The Avg. Response Time (Sec) vs Executions overtime graph displays a bar for each time slice in the selected time frame that the selected node (or part of its underlying call path) was active. These bars display a breakdown of the invoked method types according to each method type’s type's average response time. The average response time for the entire time slice is compared to the number of executions in the time slice, displayed in linear format.
...
| Info |
|---|
SLA compliance is calculated for HTTP entry points only. |
- Green. The invoked method’s method's SLA is below the defined SLA threshold.
- Yellow. The invoked method’s method's SLA is approaching the defined SLA threshold.
- Red. The invoked method’s method's SLA exceeded the defined SLA threshold.
- Blue. Top level methods that do not have SLA thresholds defined for them (for example, EJB, JDBC, and so on).
These executions will appear as “NonNon-HTTP” HTTP executions.
| Info |
|---|
Information for non-HTTP methods will not appear in the legend and in the graphs, but will appear in the ToolTip. |
...
For more information regarding findings, see “How How to identify performance problems” on page 49problems.
| Anchor | ||||
|---|---|---|---|---|
|
The Load Balance tab displays the selected entity and compares its performance in all the contexts it was invoked by in the selected time frame. If “All instances” All instances is selected in the execution tree, it will show the instances table (similar to the view provided in the Dashboard workspace).
| Info |
|---|
This tab is only displayed when “All Instances” when All instances is selected as the top level of the execution tree. When a specific instance is selected as the top level of the execution tree, this tab is not displayed. |
...
Instance. Displays the instance name. If you select the highlighted instance, the execution tree will update itself to display the specific instance’s instance's execution tree.
Info Once a specific instance is selected, the Load Balance tab will no longer appear.
- Server. Displays name of the server on which the instance is running.
- Avg. Response Time (Sec). Displays the average response time for the selected node. The average response time is displayed in seconds.
- Executions. Displays the number of executions within the selected node.
- Sum. Response Times. Displays the total response time for the selected node. The summed response time is displayed in hours: minutes: seconds: milliseconds.
...
The Impact tab displays information regarding the selected method’s method's impact on the application. It displays general performance data in context for the selected node and specific information regarding its contribution to all entry points and methods in the application by which it is directly invoked. This provides the user with a comprehensive overview of the specific method’s performance throughout the application.
...
Entry Point. Displays the name of the entry point from which the entity was invoked.
Info Selecting the hyperlinked entry point name selects the entry point in the execution tree and displays the highlights tab for the entry point.
- Work Impact on Entry Point. Displays the percent value of the selected node’s summed response time out of its entry point’s point's summed response time.
- Method Avg. Response Time (Sec). Displays the method’s method's average response time.
- Executions by Entry Point. Displays the number of times the selected method was invoked by the specific entry point.
- Sum. Method Response Times. Displays the method’s method's total response time.
- Sum. Entry Point Response Times. Displays the entry point’s total response time.
...
Caller. Displays the name of the method that directly invoked the selected method.
Info Selecting the hyperlinked direct caller name selects the method in the execution tree and displays the Highlights tabs for the method.
- Work Impact on Caller. Displays the percentage of the selected method’s method's total response time out of the direct caller method’s method's total response time.
- Method Avg. Response Time (Sec). Displays the method’s method's average response time.
- Executions by Caller. Displays the number of times the selected method was executed by the specific direct caller method.
- Sum. Method Response Times. Displays the method’s method's total response time.
- Sum. Caller Response Times. Displays the direct caller method’s total response time.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
When All Instances is the selected at the top level, this table will be is called, Heaviest Exit Points by Work Time - ones that have at least 1% impact on the total. |
...
On top appears the comparison table called “All All Methods Invoked Directly and Indirectly”Indirectly.
| Info |
|---|
This will be Heaviest methods by work time when all instances in the top level in the executions table, with 1% impact min. |
...
| Info |
|---|
The locking methods themselves are not displayed on the tree. |
The “lock” lock identifier is calculated at runtime. It is based on the object name that is being locked (synchronized). It is possible to use the same object more than once during the same method. In that case, Precise for J2EE adds an index for each of the lock events, in order to enable the developer to distinguish between the two lock events.
...
| Info |
|---|
Exceptions monitoring is turned off by default. To turn on exceptions monitoring, go to Settings>Monitor Settings > Monitor Settings. See “Configuring Monitor Settings” on page 41 Configuring Monitor Settings. |
All columns can be sorted. The default sort is by Count column.
...
On the bottom appears the title “Exception "Exception Stack Traces”Traces." This table displays information where each row is a specific occurrence of the exception selected on top. There is one row per stack trace on this table.
...
See Precise Administration Guide, Appendix A, regarding regarding configuring exception seeker options.
...
- Allocation Method. The method name where the object was allocated.
- Object Type. The object, collection, array, or string buffer. It contains values such as: “Integer”, “String”, or “MyObject”"Integer," "String," or "MyObject."
- Growth Rate. The rate that the number of objects grows over time. This is displayed in percent for growth rate per minute.
...
| Info |
|---|
Leaks monitoring is turned off by default. To turn on Leaks monitoring, go to the Settings menu. See “Configuring Monitor Settings” on page 41 Configuring Monitor Settings. |
The Leaks tab displays details about the top 64 allocation sites with the largest total live allocated objects in the selected time frame. Each allocating method displays the collection’s collection's stack trace in its ToolTip. The stack trace displays the executions leading backwards from the allocation site to the application’s application's initial execution.
For the top n allocating methods, the chart shows the approximate number of live objects in the collection, or its growth rate (according to the sorting column). Negative trends can be identified using these charts by detecting memory leaking locations.
...
| Item | Description |
|---|---|
| Chart Legend Color | Color icon showing the color representing the row in the graph. |
| Allocated Method | The method name where the object was allocated. |
| Object Type | The Object, Collection, Array, or String Buffer. It contains values such as: “Integer”, “String”, or “MyObject”."Integer," "String," or "MyObject." |
| Growth Rate (%) | Rate of growth (in percents) of the number of objects over time (objects/minutes). This column is default for sorting. |
| Live Objects Count | Number of live instances of an object. Live Objects Count can be displayed as a “waterfall” "waterfall" bar, or in numbers. |
| Anchor | ||||
|---|---|---|---|---|
|
Stack Trace details appear in the expanded view that appears when hovering over each row’s row's complete path (Stack Trace).
...
- In the Time Frame list, select the period of time you want to analyze.
- In the Instance list, select the instance you want to analyze.
- On the Precise bar, go to Settings>Tree Settings > Tree View Settings.
- In the Tree View Settings dialog box, in the Sort by drop-down list, select Executions. Click A to display in Ascending order or D to display in Descending order.
- Select the Method you want to analyze. Methods with the highest number of executions are most frequently invoked.
...