Java Profiling Workflow / Step 2 / Analyze profiling data
Analyze profiling results systematically: inventory results (flamegraphs, JFR, GC logs, thread dumps), identify problems (memory leaks, CPU hotspots, threading issues), document findings using standardized templates (profiling-problem-analysis-YYYYMMDD.md, profiling-solutions-YYYYMMDD.md), prioritize using Impact/Effort scores, and correlate multiple profiling files for validation.
What is covered in this Skill?
- Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt
- Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)
- Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md
- Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first
- Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps
Scope: Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.
Constraints
Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.
- VALIDATE: Ensure profiling results represent realistic load scenarios before analysis
- DOCUMENT: Record assumptions and limitations in analysis reports
- CROSS-REFERENCE: Use multiple profiling files to validate findings
- BEFORE APPLYING: Read the reference for problem analysis and solutions templates
When to use this skill
- Analyze JFR profile
- Profile analysis
- Performance analysis
Reference
For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.md.
1---2name: 162-java-profiling-analyze3description: Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project4license: Apache-2.05---6# Java Profiling Workflow / Step 2 / Analyze profiling data78Analyze profiling results systematically: inventory results (flamegraphs, JFR, GC logs, thread dumps), identify problems (memory leaks, CPU hotspots, threading issues), document findings using standardized templates (profiling-problem-analysis-YYYYMMDD.md, profiling-solutions-YYYYMMDD.md), prioritize using Impact/Effort scores, and correlate multiple profiling files for validation.910**What is covered in this Skill?**1112- Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt13- Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)14- Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md15- Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first16- Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps1718**Scope:** Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.1920## Constraints2122Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.2324- **VALIDATE**: Ensure profiling results represent realistic load scenarios before analysis25- **DOCUMENT**: Record assumptions and limitations in analysis reports26- **CROSS-REFERENCE**: Use multiple profiling files to validate findings27- **BEFORE APPLYING**: Read the reference for problem analysis and solutions templates2829## When to use this skill3031- Analyze JFR profile32- Profile analysis33- Performance analysis3435## Reference3637For detailed guidance, examples, and constraints, see [references/162-java-profiling-analyze.md](references/162-java-profiling-analyze.md).
jabrena