- 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
Profiler command line
Profiler command line may be useful in automation purposes or for remote profiling, when you only have console access to the remote machine and no UI is available.
Usage
Linux
<profiler directory>/bin/profiler.sh <options>macOS
<profiler directory>/Contents/Resources/bin/profiler.sh <options>Windows
<profiler directory>/bin/profiler.bat <options>Accept EULA
To accept profiler EULA without the UI, use command line option -accept-eula.
It can be used for unattended installation and in combination with other options.
Convert snapshot to HPROF
Command line can be used to create HPROF file
from an existing .snapshot file.
Enter license key
To enter license key without the UI, use command line option -license-key=<key>.
It can be used for unattended installation and in combination with other options.
Export profiling results
It is possible to export profiling results into multiple formats using just the command line.
Integration with Java servers
This article describes how to use command line to integrate profiler with Java server.
Profiling an application
Command line is enough to control profiling using HTTP API. You can also profile an already running process using attach feature.