工作模式

本地会话实时分析模式

    Profiler能够根据用户定义的启动方式进行设置。用户即刻便能从设置好的JVM中看到实时数据。用户还可以无需自定义，直接从多个IDE插件中选择进行配置。

离线分析模式

    用户无需通过JProfiler GUI连接应用程序即可对之进行设置。在离线设置模式下，用户可以使用Profiler触发系统或者JProfiler' API控制代理设置，然后保存快照。随后用户便可使用命令行导出工具或者蚂蚁任务导出工具，在JProfiler GUI或导出视图设置中打开这些快照。

内存分析

    JProfiler动态更新视图和信息视图中可显示内存使用情况。所有的视图都有几个聚集层并且能够显示现存对象和作为垃圾回收的对象。

• 所有对象
  显示类或在状况统计和尺码信息堆上所有对象的包。你可以标记当前值并显示差异值。

• 记录对象
  显示类或所有已记录对象的包。你可以标记出当前值并且显示差异值。

• 分配访问树
  显示一棵请求树或者方法、类、包或对已选择类有带注释的分配信息的J2EE组件。

• 分配热点
  显示一个列表，包括方法、类、包或分配已选类的J2EE组件。你可以标注当前值并且显示差异值。对于每个热点都可以显示它的跟踪记录树。

堆遍历

    在JProfiler的堆遍历器(Heap walker)中，你可以对堆的状况进行快照并且可以寻找感兴趣的对象。堆遍历器有五个视图：

• 类 Classes
  显示所有类和它们的实例。

• 分配 
  为所有记录对象显示分配树和分配热点。

• 索引
  为单个对象和“显示到垃圾回收根目录的路径”提供索引图的显示功能。还能提供合并输入视图和输出视图的功能。

• 数据
  为单个对象显示实例和类数据。

• 时间
  显示一个对已记录对象的解决时间的柱状图。

CPU 剖析

    JProfiler 提供不同的方法来记录访问树以优化性能和细节。线程或者线程组以及线程状况可以被所有的视图选择。所有的视图都可以聚集到方法、类、包或J2EE组件等不同层上。CPU视图部分包括：

• 访问树
  显示一个积累的自顶向下的树,树中包含所有在JVM中已记录的访问队列。JDBC,JMS和JNDI服务请求都被注释在请求树中。请求树可以根据Servlet和JSP对URL的不同需要进行拆分。

• 热点
  显示消耗时间最多的方法的列表。对每个热点都能够显示回溯树。该热点可以按照方法请求，JDBC，JMS和JNDI服务请求以及按照URL请求来进行计算。

• 访问图
  显示一个从已选方法、类、包或J2EE组件开始的访问队列的图。

线程剖析

    对线程剖析，JProfiler提供以下视图:

• 线程历史
  显示一个与线程活动和线程状态在一起的活动时间表.

• 线程监控
  显示一个列表，包括所有的活动线程以及它们目前的活动状况。

• 固定探测图表
  显示一个包含了所有在JVM里的固定的图表。、

• 目前使用的监测器
  显示目前使用的监测器并且包括它们的关联线程。

• 历史检测记录
  显示重大的等待事件和阻塞事件的历史记录。

• 监测使用状态
  显示分组监测，线程和监测类的统计监测数据。

VM 遥感勘测技术

    观察JVM的内部状态，JProfiler提供了不同的遥感勘测视图，如下所示:

• 堆
  显示一个堆的使用状况和堆尺寸大小活动时间表。

• 对象
  显示一张关于活动对象与数组的图表的活动时间表。

• 垃圾收集器
  显示一张关于垃圾回收活动的活动时间表。

• 类
  显示一个与已装载类的图表的活动时间表。

• 线程
  显示一个与动态线程图表的活动时间表。
  

JProfiler支持平台

Windows macOS Linux FreeBSD Solaris AIX HP-UX

Modes of Operation

Live profiling of a local session

Once you define how your application is started, JProfiler can profile it and you immediately see live data from the profiled JVM. To eliminate the need for session configuration, you can use one of the many IDE plugins to profile the application from within your favorite IDE.

Offline profiling and triggers

You do not have to connect with the JProfiler GUI to the profiled application in order to profile it: With offline profiling you can use JProfiler's powerful trigger system or the JProfiler API to control the profiling agent and save snapshots to disk. At a later time you can open these snapshots in the JProfiler GUI or programmatically export profiling views with the command line export tool or the export ant task.

Memory profiling

JProfiler's memory view section offers dynamically updated views on memory usage and views that show information about allocations spots. All views have several aggregation levels and can show live and garbage collected objects

• All objects
  Shows classes or packages of all objects on the heap with instance counts and size information. You can mark current values and show differences.。

• Recorded objects
  Shows classes or packages of all recorded objects. You can mark current values and show differences.

• Allocation call tree
  Shows a call tree or methods, classes, packages or Java EE components with annotated allocations of selected classes.

• Allocation hot spots
  Shows a list of methods, classes, packages or Java EE components that allocate selected classes. You can mark current values and show differences. The tree of backtraces can be shown for each hot spot.

Heap Walker

In JProfiler's heap walker you can take a snapshot of the heap and drill down to objects of interest by performing selection steps. The heap walker has five views:

• Classes
  Shows all classes and their instances.

• Allocations
  Shows allocation tree and allocation hot spots for recorded objects.

• References
  Shows outgoing references for individual objects with primitive data and incoming references with "show path to garbage collector root" functionality. Also offers cumulated views for incoming and outgoing references. In the outgoing references view, you can apply filters. There are two different filter types: Filtering by primitive values and filtering with a script.

• Data
  Shows instance and class data for individual objects.

• Time
  Shows a time-resolved histogram of recorded objects.

CPU profiling

JProfiler offers various ways to record the call tree to optimize for performance or detail. The thread or thread group as well as the thread status can be chosen for all views. All views can be aggregated on a method, class, package or Java EE component level. The CPU view section contains:

• Call tree
  Shows a cumulated top-down tree of all recorded call sequences in the JVM. JDBC, JMS and JNDI service calls are annotated into the call tree. The call tree can be split for different request URL to a servlet or JSP. You can mark methods for "exceptional method run recording" and see the slowest invocations separately. With request tracking, you can connect call sites to execution sites in multi-threaded applications.

• Hot spots
  Shows the list of the most time consuming methods. The tree of backtraces can be shown for each hot spot.

• Call graph
  Shows a graph of call sequences starting from selected methods, classes, packages or Java EE components.

Thread profiling

For thread profiling, JProfiler offers the following views:

• Thread history
  Shows a time line with thread activity and thread status.

• Thread monitor
  Shows a list of all live threads with their current activity.

• Thread dumps
  You can take multiple thread dumps and analyze them in the thread dumps view.

VM telemetry

To observe the internal state of your JVM, JProfiler offers various telemetry views:

• Heap
  Shows a time line with a graph of the used heap and the heap size.

• Recorded objects
  Shows a time line with a graph of live objects and arrays that have been recorded.

• Recorded throughput
  Shows a time line with a graph of the rates of object creation and garbage collection for recorded objects.

• Classes
  Shows a time line with a graph of loaded classes.

• Threads
  Shows a time line with a graph of active threads.