- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Running applications with the profiler
- Connect to profiled application
- Troubleshoot connection problems
- Solving performance problems
- CPU profiling
- 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
- IDE integration
- Time measurement (CPU time, wall time)
- 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
- FAQ: How to profile in my scenario?
Profiler is able to use HTTP or SOCKS v5 proxies to establish outgoing HTTPS connections. The proxy settings can be configured at Setting | Proxy... menu.
Automatic proxy detection
By default profiler tries to obtain proxy settings automatically from the system setting of your OS, from your default web browser, etc. For different operating systems profiler uses different detection strategies, so detection should work well in most cases. But you can always configure the settings manually.
Profiler supports a proxy auto-config PAC files, which define how profiler chooses the proxy server for fetching a given URL. To use this method you should specify the URL of your PAC file.
Manual method allows to specify proxy type (HTTP or SOCKS v5), as well as host and port which proxy server listens.
In this mode the profiler always tries to establish direct connection.
If your proxy server requires authentication, please check Proxy requires authentication checkbox and provide the user name and password.