Key Performance Findings Report.
The report focuses on the key indicators of the monitored case and significantly reduces the time required to analyze collected information and identify bottlenecks.
It features the areas that influence performance of the application the most, whether it is individual execution or cumulative impact on the system due to high frequency of
use, and/or areas that create abnormally high load on the system as a whole.
System Alerts - Alerts section lists events with execution time or resource utilization exceeding predefined thresholds.
Resources Utilization - The CPU graph shows total general CPU utilization by Java Virtual Machine (JVM), as well as consumption by the most demanding individual threads within JVM, as the percentage of the total server's
CPU.
Resources Utilization - The Memory graph shows memory utilization by the Java Virtual Machine. Memory consumption is expected to grow until it is released by the garbage collector (GC). Up and down fluctuations are normal and indicate that the system is healthy. However, behavior when memory drops to increasingly higher level and oscillations grow shorter, while top line lingers around maximal available memory, may indicate memory leak in the system, or simply higher demand that JVM can
provide. In such case, the execution of the application is constrained by total available memory and JVM might eventually crash.
User Experience - Additional factors that may impact user experience are network latency and browser-side processing time. The execution time shown on the graph represents minimum user wait time which could be
achieved when user has adequately equipped workstation and negligible network delays.
Heavy Methods - The section lists twenty methods with the longest execution time, along with the details pinpointing the reasons.
For each of the listed in the table methods, report offers additional supporting information about repeatedly executed sub-methods, methods with highest net execution time, methods causing the highest CPU utilization, total time spent on database queries and the Heaviest SQL queries.
Heavy Methods by Total Net - The section lists the methods with longest total net time, which are directly responsible for the duration of the execution.
Net time is calculated as full duration time minus full duration time of methods that are called directly from the method in question. The list could contain low-level methods, including I/O methods and other
event waits.
All Queries Totals - The section highlights portion of the overall execution time that was spend on database queries.
The data could be one of the quick indicators on whether the performance issues are database related.
Heavy Queries by Total Duration - While one execution of the query doesn't take long time to execute, the queries listed in this section were executed enough times to account for the significant total execution time.