Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Java EE high-level statistics

You can profile applications in high-level terms like SQL statements and URLs.

High-level statistics depends on corresponding built-in probes whose activity mode is Auto by default, which means they are active only while CPU profiling is running, in either CPU sampling or CPU tracing mode. If neither CPU tracing nor CPU sampling was running, high-level profiling results are not available.

This statistics is not available in live views. To access it, capture and open a snapshot, then switch to the "Java EE statistics" view:

The view consists of the following sections:

  • Database

    Shows database requests and their invocation method back traces.

    You can see the requests as a plain list or group them by type.

    Supported databases:

    • JDBC (SQL)
    • MongoDB (Java driver version 3.0 and newer are supported)
    • Cassandra
    • HBase
    • Java persistence (JPA): Hibernate, EclipseLink, OpenJPA, DataNucleus
  • JSPs and Servlets

    Shows list a of URLs that correspond to JSP and Servlet calls, and merged callees for all methods invoked with these URLs

  • JNDI

    Shows list of URLs that correspond to JNDI calls, and back traces for all methods invoked with these URLs

For each Java EE call CPU time and invocation count are reported.

Java EE profiling requires bytecode instrumentation and adds some additional overhead to the profiled application. For detailed information, see Profiling overhead: how to reduce or avoid

Lines can be copied to clipboard by using File | Copy to Clipboard (Ctrl + C):