- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Virtual threads support
- Object allocation profiling
- Memory profiling
- Monitor profiling
- Exception profiling
- Telemetry
- Probes: monitor events of various kinds
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary
- Filters
- Profiler command line
- Export of profiling results to external formats
- Profiler Java API
- Profiler HTTP API
- Settings
- Troubleshooting and FAQ
Start profiling
There are multiple ways to profile a Java application. Some may be more suitable than other, depending on the application type or the environment in which and how it is running.
Profiling in IDE
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.
Profiling a Java server
If you want to profile a standalone Java server, for example Tomcat or Jetty, you can use Java server integration wizard.
Profiling a running application
You can attach profiler to any Java application, even if it is already running.
Profiling a remote application
Profiling can be done remotely when an application runs on another computer.
Profiling in Docker
Follow these instructions on how to profile a Java server or application running in Docker container.
Profiling in Amazon EC2 instance
Follow these instructions on how to profile in Amazon EC2 instance.
Profiling Java application from command line
If none of the above methods suit your needs, you can always manually enable profiling for any Java application using command line JVM options.