- 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
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
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.
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.
Profiling an application
Command line is enough to control profiling using HTTP API. You can also enable profiling with command line tool.