skills.rest
ririnto
ririntoCOMMUNITY
Explore all skills by this author →
GitHub

jvm-gc-diagnostics

Analyzes JVM garbage-collection behavior and collector tradeoffs from GC logs and JFR data for Java LTS baselines 8-25.

Updated Apr 9, 2026
Search Tags:#troubleshooting#jvm#analyze#garbage-collection#jfr#gc-logs#collector-tradeoffs
One-click install
npx skills add https://github.com/ririnto/sinon --skill jvm-gc-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jvm-gc-diagnostics
Source: https://github.com/ririnto/sinon/tree/main/plugins/jvm/skills/jvm-gc-diagnostics
Command: npx skills add https://github.com/ririnto/sinon --skill jvm-gc-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyze JVM garbage-collection behavior, collector tradeoffs, and runtime evidence to triage GC-related performance issues.

Core Features & Use Cases

  • Read GC configuration, collect logs, and interpret GC events across JDK versions.
  • Compare collectors (G1, ZGC, CMS, Shenandoah) against observed runtime behavior using GC logs and JFR data.
  • Use-case: When an application experiences pauses or heap pressure, extract evidence and propose targeted tuning actions.

Quick Start

Analyze GC behavior for a running Java process and report the active collector and longest pause.

Frequently Asked Questions about jvm-gc-diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze JVM garbage collection logs to find the cause of long pauses?▼

To analyze JVM garbage collection logs, you provide runtime GC data and align it with your Java LTS baseline. This extracts evidence from GC logs and JFR recordings to identify collector tradeoffs and guide targeted performance optimization for pause issues.

What is the best way to compare G1, ZGC, and Shenandoah collectors for my application?▼

Comparing G1, ZGC, and Shenandoah collectors involves evaluating their tradeoffs against observed runtime behavior. Analyzing GC logs and JFR data triages heap pressure and pauses to determine the optimal collector choice for your application.

Can I use JFR data to triage heap pressure across different Java LTS versions?▼

You can use JFR data to triage heap pressure across Java LTS baselines 8, 11, 17, 21, and 25. The analysis requires runtime GC data including JFR recordings and jcmd VM.flags to provide evidence-based recommendations for your specific version.

How do I diagnose JVM GC behavior for a running Java process?▼

Diagnosing JVM GC behavior for a running process involves collecting runtime evidence such as GC logs, jcmd VM.flags, VM.command_line, and JFR recordings. This data is interpreted across JDK versions to report the active collector and longest pause.

What runtime data is required to tune garbage collection and optimize collectors?▼

Tuning garbage collection requires runtime GC data including GC logs, jcmd VM.flags, VM.command_line, and JFR recordings. This evidence must align with your deployed Java LTS baseline to accurately triage pauses and propose targeted tuning actions.

Related Skills

Explore More Software Engineering Skills→
ririntoririnto

jvm-runtime-diagnostics

Diagnose JVM runtime incidents using jcmd, jhsdb, and JFR.

Community
Advanced
iceflowericeflower

jvm-performance

Diagnose JVM performance bottlenecks by analyzing GC behavior, heap usage, and runtime metrics.

Community
Advanced
yzavyasyzavyas
7

build-jvm-analysis

Profile JVM applications with async-profiler and JFR to identify bottlenecks and memory leaks.

Community
Advanced
adrianprecubadrianprecub

jvm-diagnostics

Analyze JVM diagnostic files to detect performance issues and generate reports.

Community
Advanced