gc-memory

Interpret .NET runtime GC and memory metrics to diagnose memory pressure and leaks.

12|2|Updated May 4, 2020
One-click install
npx skills add https://github.com/hoangnh2412/jarvis --skill gc-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gc-memory
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/analyze-metric-dotnet/providers/gc-memory
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill gc-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork involved in diagnosing .NET application memory pressure, garbage collection (GC) pauses, and potential memory leaks by providing clear, structured guidance for interpreting core runtime GC and memory metrics.

Core Features & Use Cases

  • Metric Interpretation: Breaks down key GC and memory metrics including collection counts per generation, heap size, committed memory, pause time, and allocation rate, with explanations of their significance.
  • Anomaly Pattern Recognition: Guides users to distinguish normal traffic-related metric spikes from long-term issues like memory leaks or unoptimized caching, with clear actionable suggestions for each pattern.
  • Use Case: For example, a developer investigating intermittent high API latency can use this Skill to correlate GC pause time spikes with P99 response times to confirm if GC pressure is the root cause of the performance issue.

Quick Start

Use the gc-memory skill to analyze your .NET application's GC and memory metrics to identify the root cause of increased latency or unexpected memory growth.

Frequently Asked Questions about gc-memory

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

FAQPage Schema
How do I diagnose .NET GC pauses causing high API latency?

Identify .NET memory leaks by analyzing heap size trends and committed memory metrics. This Skill helps distinguish normal transient traffic spikes from long-term memory issues like unoptimized caching.

What do .NET garbage collection collection counts per generation indicate?

Collection counts per generation indicate garbage collection frequency and memory pressure levels. This Skill breaks down key GC metrics to explain their significance for .NET application performance.

How do I distinguish normal traffic spikes from memory pressure in .NET?

Distinguish normal traffic spikes from memory pressure by recognizing anomaly patterns in allocation rates and heap size metrics. This Skill provides actionable suggestions for each detected pattern.

Can I use PromQL metrics to troubleshoot .NET memory leaks in production incidents?

Apply .NET GC diagnostic guidance proactively for memory usage monitoring by tracking heap size trends and pause times. This Skill satisfies proactive monitoring requirements to prevent long-term memory issues.