Disabling profiling features in session configuration

## Disabling profiling features in session configuration |
previous | up | next

| On this tab of the profiling settings dialog, you can adjust profiling features of JProfiler in order to speed up program execution and reduce memory consumption.

| Disabled profiling features Disable call tree collection If you don't need CPU profiling data as well as the allocation view in the heap walker, the allocation monitor view and the stack trace information in the monitor usage views, you can switch off the 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 monitor The information depth of the allocation monitor view is governed by this setting. Show cumulated allocations of all classes The [Change Selection] in the allocation monitor and the allocation hot spots view will not work in this setting, only the cumulated allocations of all classes and array types can be displayed. Show allocations resolved for each class The [Change Selection] in the allocation monitor and the allocation hot spots view is enabled this setting, single classes, array types and packages can be displayed by the allocation monitor view. Memory consumption is increased by this setting. Disable allocation monitor The allocation monitor and the allocation hot spots view will be disabled. This setting speeds up the profiling of your application and reduces the memory overhead.

| Invocation tree By default, JProfiler does not resolve line numbers in call trees. If you enable `show line numbers for sampling and dynamic instrumentation`, line number resolution will be enabled for the call tree collections modes of "Sampling" and "Dynamic instrumentation". For "Full instrumentation", line number resolution is not available. When a method calls another method multiple times in different lines of code, line number resolution will show these invocations as separate method nodes in the invocation tree and the allocation monitor view. Backtraces in the hotspot views will also show line numbers. Note that a line number can only be shown if the call to a method originates in an unfiltered class.