## Live Profiling Results Window - Memory Usage

See Also

The results that are displayed in the Live Profiling Results window depend upon which profiling task is in progress. When you analyse memory usage, the window displays data on object allocation and liveness. The profiling results displayed depend on which of the following options you choose.

### Record object creation only

When you choose this option, the Profiling Results window displays a list of classes (including array classes), with the total size and number of instances that have been allocated since you issued the instrumentation command. All classes currently loaded by the target JVM (and each new class as it is loaded) are instrumented.

When you choose this option, the Live Profiling Results window displays the following information for each profiled class:

- Bytes Allocated. This is a graphical representation of the percentage of bytes allocated.
- Bytes Allocated. This is the actual number of bytes allocated and the percentage of total bytes.
- Objects Allocated. This is the number of live objects and the percentage of the total number of objects.

Right-click a class name to access the following popup menu commands.

- Go To Source. Select this to open the source `.java` file for the selected class in the Source Editor.
- Log Class History. Select this to display the history for the selected instance.

### Record both object allocation and garbage collection

When you choose this option, the Live Profiling Results window displays the following information:

- Live bytes. This is a graphical representation of live bytes.
- Live bytes. This is the actual number of live bytes.
- Live Objects. This is the size and number of live
  for the given class at the moment. You can set the proportion of objects that are tracked when you configure the profiling session.
- Allocated objects. This number is the total number of tracked objects that have been allocated.
- Average object age. This number is the average age for the live tracked objects of this class, measured as the number of garbage collections that the object has survived.
  - The IDE does not distinguish between partial (young generation) and full garbage collections if a generational garbage collector is used.
- Generations. This is the number of survived generations and represents the total number of different object ages for objects of this class.
- Total number of allocated objects. This number is the total number of allocated objects for this class.

The following popup menus are available when you right-click a class name.

- Go To Source. Select this to open the source `.java` file for the selected class in the Source Editor.
- Log Class History. Select this to display the history for the selected instance.
- Stop Profiling this Class.
- Stop Profiling Classes Below this Line.

Limiting the profiled classes to only those you are interested in can help reduce the profiling overhead.

The following popup menu item is also available when you select the Record Stack Traces option.

- Take Snapshot and Show Allocation Stack Traces.

For more on how object liveness data is tracked and collected, see the following NetBeans FAQs:

See Also
  Analyzing Application Memory Usage
  Working with Live Profiling Results
  About Profiling Results

Legal Notices