- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- IDE integration
- Java server integration wizard
- Attach profiler to a running application
- Attaching from profiler UI
- Console attach wizard
- 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?
Console attach wizard
Console wizard might be useful if you want to profile remote Java server or the machine has no graphics environment.
Running the wizard
Install profiler on the machine where your Java application is running. License key is not required to use the wizard.
Run the command below:
On Windows
<Profiler Installation Directory>\bin\attach.bat
or
<Profiler Installation Directory>\bin\attach.bat <PID>
or
<Profiler Installation Directory>\bin\attach.bat <PID> <startup_options>
On macOS
<Profiler Installation Directory>/Contents/Resources/bin/attach.sh
or
<Profiler Installation Directory>/Contents/Resources/bin/attach.sh <PID>
or
<Profiler Installation Directory>/Contents/Resources/bin/attach.sh <PID> <startup_options>
On other platforms
<directory with unpacked content>/bin/attach.sh
or
<directory with unpacked content>/bin/attach.sh <PID>
or
<directory with unpacked content>/bin/attach.sh <PID> <startup_options>
<PID>is an optional parameter.
Specify it to immediately attach the agent to particular application.
If <PID> is not specified,
the wizard will show the list of running JVMs
and offer to choose to which JVM to connect.
<startup_options>
is an optional parameter to specify additional startup options.
If <PID> parameter is not specified,
the wizard will offer to specify startup options.
Follow the instructions that will appear:
After the profiler agent is attached, its port will be printed out. Use this port number to connect to the application and start profiling.