- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- IDE integration
- Java server integration wizard
- Attach profiler to a running application
- Remote profiling
- Docker
- Enabling profiling manually
- Startup options
- Connect to profiled application
- Profiling troubleshooting
- Profiling overhead: how to reduce or avoid
- Solving performance problems
- CPU profiling
- Threads
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Time measurement (CPU time, wall time)
- Filters
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler Java API
- Profiler HTTP API
- Command line tool to control profiling
- Settings
- FAQ: How to profile in my scenario?
Start profiling
You have different options to start profiling of your application:
-
Profiler has seamless integration with most popular Java IDEs. After installing the plugin, you will be able to profile all types of Java applications right from IDE.
-
If you want to profile a standalone Java server (Tomcat, Jetty, etc) or an application, you can use Java server integration wizard.
-
Attach profiler to a running application.
-
Profiling can be done remotely when applications run on another computer.
-
Manually enable profiling of your application.