所有的方法调用都会被跟踪，这样可以监控到JAVA核心类(java.*),但比动态获取慢，尤其是1.4 JVMs 。在1.5 JVMs (JVMTI)中不能使用。 使用全部获取你可以随意地显示具体的类调用的方法而不是某个方法在哪个类中实现。
活动过滤设置( active filter sets )
??Exclusive(独占的)
在下表中，你为会话选择哪些过滤集是活动的。这些过滤器指定CPU监控的结束点。在包或类中匹配过滤集中的某一个，进一步的调用其它被过滤的类将在调用第一个被过滤的方法时失败。在被过滤的类中，方法是不透明的并且在call tree view中标为红色.
过滤集可以在general settings的\标签中设定。
??Inclusive(包含的)
输入逗号分隔类和包的过滤器。在CPU监控中，只有符合这些包或类的调用才能够被显示。
例如，如果你指定com.mycorp.,com.othercorp. 作为一个包含的过滤器，一个调用com.mycorp.MyClass.myMethod() 和它做的所有调用才会被度量和显示。而所有从 com.mycorp.MyClass.myMethod() 发起的调用都不属于包com.mycorp 和com.othercorp ，它们是不透明的并且在call tree view.标识为红色。
6.2.3 JAVA 子系统
在此标签下，你可以选择JProfiler如何记录J2EE相关的JAVA子系统。 ",记录服务调用
JProfiler 使用仪器监控几个J2EE服务层并记录象服务调用的执行时间等语义数据。记录仪器不需要依赖，可以为所有驱动或服务提供商工作。服务调用在call tree view中有解释并且可以在hot spot view选为热点。 下面的服务类型可以被单独激活： ",JDBC calls ",JMS calls
JNDI calls ",J2EE awareness
如果选择了Split call tree for each request URL ， JProfiler将分析调用servlets 和 JSPs的URL。针对每个URL，在call tree中都创建一个新的节点。URL也能够在hot spot view选择成了一个热点类型。这样做的话，你可以在单独的页面或请求中区分性能问题。
缺省，只有没有查询参数的URL会使用上面的分离进程。为了在call tree中保留选择的参数，你可以在retained request parameters文本框中输入要保留的参数。
如果要显示所有的请求，请选择Show request URLs that are outside the call tree.
6.2.4 features
",Enabled profiling features
在此标签中，你可以调整监控的属性，以提高软件执行速度，减少内存使用。
Disabled profiling features
Disable call tree collection When you record CPU data or allocations, JProfiler collects information about the call tree. You might want to record allocations without the overhead of recording the allocation call stacks: If you don't need the allocation view in the heap walker, the allocation call tree and the stack trace information in the monitor usage views, you can
switch off call tree collection. This will speed up profiling considerably and reduce memory usage.
Disable monitor contention views if you are not interested in monitor contention events, you may switch data collection off by selecting this checkbox to lower the memory consumption of the profiled application. If monitor contention views are enabled, the following settings govern the level of detail for the monitor contention views:
",Monitor contention threshold
Select the minimum time threshold in microseconds (μs) for which a monitor contention (i.e. when a thread is blocking) is displayed in the monitor usage history view.
",Monitor waiting threshold Select the minimum time threshold in microseconds (μs) for which a monitor wait state (i.e. when a thread is waiting) is displayed in the monitor usage history view.
? Allocation call tree The information depth of the allocation call tree and the allocation hot spots view is governed by this setting.
Live objects By default, only live objects can be displayed by the allocation views. Class-resolution is enabled.
Live and GCed objects without class resolution Live and garbage collected objects can be displayed by the allocation views, depending on the selection in the allocation options dialog. Class-resolution is disabled, i.e. class selection in the allocation options dialog will not work in this setting, only the cumulated allocations of all classes and array types can be displayed. This setting consumes more memory than the first setting and adds a considerable performance overhead.
Live and GCed objects Live and garbage collected objects can be displayed by the allocation views, depending on the selection in the allocation options dialog. Class-resolution is enabled. This setting consumes more memory than the other settings and adds adds