Description: The Method Profiling page contains information about sampled stack traces.

Go to primary content

| Previous | Next |

# Using the Method Profiling Page

The Method Profiling page contains information about sampled stack traces.

This page displays method profiling information in tables.

The method profiler does not require threads to be at safe points in order for stack traces to be sampled. However, since the most common case is that stacks will only be walked at safe points, the Java HotSpot Virtual Machine normally does not provide metadata for non-safe point parts of the code. This means that such samples will not be properly resolved to the correct line number and BCI unless you specify:

    -XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints

With `DebugNonSafepoints`, the compiler will additionally generate the necessary metadata for the parts of the code not at safe points.

Using the Method Profiling Page: Selections and Aspects

Use the drop-down menus at the top of the page to choose a selection and aspect if desired. Data from other pages can be saved to the selection drop-down menu by dragging an area of a chart (or selecting data from a table) and choosing Store Selection or Store Selection and Set As Focused Selection from the context menu.

The following controls provide additional behavior:

- Show concurrent: Show all events concurrent to the selected aspect.

- Intersecting: Show all events that intersect the original events, or only those contained in the same timespan.

- All threads: Show events in all threads or only in threads related to the original events.

Using the Method Profiling Page: Tables

Table columns are labeled as follows:

- Package: The fully qualified package name.

- Class: The fully qualified class name.

- Count: The number of times that methods were sampled.

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | Previous | Next |