Heap Walker

Use the Heap Walker to evaluate the Java heap contents and to identify unnecessary references that cause memory leaks. You can browse classes and instances of classes on the heap, fields of each instance or class, and references to each instance.

Profiling Points

Place profiling points in your source code to more precisely control the collection of profiling results, similar to debugger breakpoints.

You use profiling points to automatically trigger actions when certain conditions are met, such as execution of a line of code, time elapsed, or memory used. Profiling points can trigger heap dumps, the reseting of results collected, the running of a load generator script, and the taking of a results snapshot.

Identifying CPU Bottlenecks

The NetBeans profiler can be set up to report only on particular methods or the entire application. A graph categorizes where CPU time has been spent. Click on the graph sections to drill down from high-level categories to more detailed profiling information.

Profile an entire application, or a subset, under a realistic workload. You can do load testing by starting JMeter scripts at the beginning of a profiling session.

Tracking Memory Usage

Pinpoint leaking objects based on their special pattern of allocations and garbage collections, or lack thereof. Object liveness profiling tracks both object creation and garbage collection events. Watch the number, age, allocation paths, and other characteristics of objects currently in memory and compare memory snapshots.

Monitoring Threads Status

On the Threads Timeline, the NetBeans profiler displays the current and past status of all threads in an application. Thread Details give you detailed information about one or more selected threads, including a list of all state changes in the thread life.

Remote Profiling

Profile an application that is running on a different system than your NetBeans IDE. The profiler's remote pack can be installed on a remote system, allowing you to profile an application that is started on that system.

Attach Profiler

Attach the profiler to any Java application, even applications that are not started by the IDE. If the Java application and the IDE are both run with JDK 6, you can even attach the profiler dynamically, allowing you to do profiling of an application that is already running.