This section includes the following topics:
In most cases, a Precise TPM tab displays information in the context of a specific application and time frame. However, if you want to view findings for another time frame or application, you can change these settings using the respective dropdown lists. See About TPM findings.
When investigating finding, it is recommended to investigate findings based on their severity.
To investigate a finding
Several tab findings exist in the Findings table to help the user.
The following is a list of current Precise TPM findings for an instance/method:
A high work time for a specific hotspot (reflecting the hotspot's work time only, without the underlying call path), can indicate a performance issue within the context of that hotspot.
In the same way, a high work time for a specific occurrence of a hotspot invoked multiple times in the invocation tree can indicate a performance issue within the context of that specific occurrence.
To effectively locate the root cause of the performance finding, examine the heaviest occurrences further by following the featured link.
The invocation tree opens to the hotspot's heaviest call path, facilitating effective navigation to the root cause. Examine the information displayed and look at the overtime graph and findings to drill down further to find the root cause of the performance issue.
By default, information is displayed for the heaviest hotspot's call path. To investigate the other call paths, select them from the invocation tree. (They are highlighted in bold). |
SLA thresholds are defined to help the user pinpoint transactions experiencing performance issues according to specific criteria. Frequent SLA breaches and near breaches can be caused by an underlying performance issue.
To effectively locate the root cause of the performance finding, perform one of the following:
This Application has undergone an upgrade with Precise 9.6.x, but not all of the instances were upgraded. Therefore, statistics data will be displayed only for instances that have either been upgraded, or are newly installed.
To effectively locate the root cause of the performance finding, perform the following:
This section contains information about the Starved Virtual Machine finding in Precise TPM.
CPU Ready time is the amount of time that a guest virtual machine is ready to run against the physical CPU. However, the VMware CPU Scheduler cannot find time to run the virtual machine because other virtual machines are competing for the same resources. CPU Ready time can be an indicator of saturation on a system.
To effectively locate the root cause of the performance finding, perform the following:
This section contains information about the VM Memory Swapping finding in Precise TPM.
Swap wait time is the time CPU waited for memory swap-in. Memory swapping almost always causes performance problems with the virtual machine whose memory is being swapped. It can also cause performance problems for other virtual machines due to the added overhead of managing swapping. VMware ESX uses swapping as a last resort to maintain correct operation of virtual machines when there is insufficient memory available to meet the needs of all virtual machines simultaneously.
The basic cause of memory swapping is memory over-commitment using virtual machines with high memory demands.
To effectively locate the root cause of the performance finding, perform the following:
This section contains information about the Virtualization Events Detected finding in Precise TPM.
Virtual machine events inform you of anything that occurs during the lifetime of a virtual machine. Any event on your application's virtual machines is something that is irregular and should be considered when checking performance issues.
To effectively locate the root cause of the performance finding, examine the events that occurred for the application's virtual machines. Look for any changes in the performance graphs to see if the events might have had any influence on the virtual machine's behavior.