- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- IDE integration
- Java server integration wizard
- Attach profiler to a running application
- Remote profiling
- Profiling in Docker container
- Profiling in Amazon EC2 instance
- Enabling profiling manually
- Startup options
- Connect to profiled application
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Virtual threads support
- Deadlock detector
- Memory profiling
- Garbage collection
- 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
IntelliJ IDEA
CPU and memory profiling has never been easier and smarter at the same time with using YourKit with the IntelliJ IDEA IDE. YourKit Java Profiler brings new functionality to IntelliJ IDEA and adds the ability to profile complex Java EE and desktop applications with just a single click. YourKit Java Profiler adds a new Profile action in all places where you usually find Run or Debug within the IDEA environment.
IntelliJ IDEA requirements
YourKit Java Profiler has integration with IntelliJ IDEA 2020.3 - 2024.3 and JetBrains Toolbox 2.0.
Plugin installation
To enable integration, you should install the profiler plugin. Use Profile from within the IDE... action on Welcome screen or in Tools menu.
Choose IntelliJ IDEA and follow the instructions.
Profiling from IDEA
After the plugin is installed, Profile actions appear in the toolbar, in the main menu, and in context menus.
To configure the profiler parameters:
- Open the Run/Debug Configurations dialog.
- Select the run configuration.
-
Click the link Modify options and select the item Profile in the Startup/Connection section of the drop-down list.
The Profile action starts the profiled application, and connects to it from the profiler UI, unless the opposite is configured. Furthermore, the application will appear in Monitor Applications list on Welcome screen.
Navigation action
While profiling, you usually need to browse the related source code to understand the performance problems at hands. After the problem is located, you edit the source code to fix it.
Use Tools | Open in IDE (F7) to open the underlying source code in the editor of your IDE - the best place to browse and edit code.
The navigation action works on the current selection and is available in both CPU and memory views. Additionally, it offers the extremely useful ability to locate the code of anonymous classes and their methods, a task that is typically very challenging to accomplish manually.
