Quickstart
Este conteúdo não está disponível em sua língua ainda.
Quickstart Guide
Section titled “Quickstart Guide”Get up and running with GalataJ in just a few minutes.
You won't need the terminal
Most users never need the CLI. The IDE plugin handles setup, profiling, and everything else automatically. Just install, click, and see your metrics.
Step 1: Install the Plugin
Section titled “Step 1: Install the Plugin”IntelliJ IDEA
Section titled “IntelliJ IDEA”- Open File → Settings → Plugins
- Search for “GalataJ”
- Click Install and restart the IDE
VS Code / Cursor
Section titled “VS Code / Cursor”- Open Extensions (Ctrl+Shift+X)
- Search for “GalataJ”
- Click Install
Step 2: Start Profiling
Section titled “Step 2: Start Profiling”IntelliJ IDEA
Section titled “IntelliJ IDEA”- Run your Java application normally
- Go to Run → Start GalataJ Profiling
- Select the JVM you want to profile
- Click Start
That’s it! The plugin automatically:
- ✅ Starts the controller (if needed)
- ✅ Discovers running JVMs
- ✅ Attaches the profiler agent
- ✅ Begins collecting metrics
VS Code / Cursor
Section titled “VS Code / Cursor”- Run your Java application
- Open Command Palette (Ctrl+Shift+P)
- Run “GalataJ: Start Profiling”
- Select the JVM from the list
Step 3: View Metrics
Section titled “Step 3: View Metrics”Once profiling is active, you’ll see performance metrics directly in your code:
What you’ll see:
- Execution time - Average and max time per method call
- Call count - How many times the method was called
- Trend - Performance change compared to previous measurements
- Memory allocations - Bytes allocated per call
Profiler Panel
Section titled “Profiler Panel”Open the Profiler panel for detailed statistics:
Inline Hints
Performance metrics appear directly above each method in your code editor
Profiler Panel
Detailed view with sorting, filtering, and historical data
Step 4: Stop Profiling
Section titled “Step 4: Stop Profiling”When you’re done:
IntelliJ: Go to Run → Stop GalataJ Profiling
VS Code: Command Palette → “GalataJ: Stop Profiling”
Next Steps
Explore more features and integrations.
Something Not Working?
Section titled “Something Not Working?”Quick Fix: Run Doctor
If the IDE can’t find your JVM or profiling doesn’t start, open a terminal and run:
galataj doctorThis checks your system setup and tells you exactly what’s wrong.
Common issues:
- JVM not showing up? Make sure your Java app is running, then try Refresh JVMs in the plugin
- No metrics appearing? Check that the Profiler panel is open and profiling is active
- Plugin not working? Restart the IDE after installation
For more help, see the Troubleshooting Guide.