OpenSkillIndex← back to search
claude-codedevelopment

Cursor-rules-java 162-java-profiling-analyze

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 project

install
source · Clone the upstream repo
git clone https://github.com/jabrena/cursor-rules-java
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/jabrena/cursor-rules-java "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/162-java-profiling-analyze" ~/.claude/skills/jabrena-cursor-rules-java-162-java-profiling-analyze && rm -rf "$T"
manifest: skills/162-java-profiling-analyze/SKILL.md
tags
#java#profiling#performance#memory#debugging#analysis
source content

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
  • Analyze the profile
  • Analyze the performance
  • Analyze the memory
  • Analyze the threading
  • Analyze the GC
  • Analyze the profiling
  • Analyze the profiling
  • Performance analysis

Reference

For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.md.