golang-performance

Identify Go performance bottlenecks with profiling-first workflows and repeatable benchmarks.

5|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/omarluq/og-template --skill golang-performance-omarluq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-performance
Source: https://github.com/omarluq/og-template/tree/main/.agents/skills/golang-performance
Command: npx skills add https://github.com/omarluq/og-template --skill golang-performance-omarluq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Golang-performance optimization patterns and methodology help engineers fix real bottlenecks after profiling, rather than guessing at micro-optimizations.

Core Features & Use Cases

  • Profiling-first patterns for allocations, CPU hot paths, memory layout, GC tuning, pooling, and caching.
  • Iterative methodology: measure baseline, diagnose with pprof/benchstat, apply a single change, and re-measure.
  • Use cases: when a service shows high allocations, CPU-bound hot loops, or GC pressure, and you need repeatable improvements with evidence.

Quick Start

Run a profiling pass on your Go project and apply one optimization pattern at a time, then re-measure the impact.

Frequently Asked Questions about golang-performance

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

FAQPage Schema
How do I identify Go performance bottlenecks using profiling?

Identify Go performance bottlenecks by enforcing a profiling-first workflow using pprof to diagnose CPU hot paths and memory allocations, rather than guessing at micro-optimizations.

What is the best way to reduce high allocations in a Golang service?

The best way to reduce high allocations in a Golang service is to apply pooling and caching patterns iteratively, measuring the baseline with benchstat and validating improvements after each change.

How do I tune the garbage collector for GC pressure in Go?

Tune the garbage collector for GC pressure in Go by applying GC tuning patterns after diagnosing memory layout and allocation hot spots through repeatable benchmarks and profiling.

Why should I use a profiling-first workflow for Golang optimization?

A profiling-first workflow for Golang optimization ensures you fix real bottlenecks with evidence, preventing wasted effort on micro-optimizations that do not impact CPU hot paths or memory layout.

Can I validate Golang performance improvements without repeatable benchmarks?

Validating Golang performance improvements requires repeatable benchmarks to measure the baseline, apply a single change, and re-measure the impact to ensure accurate, evidence-based results.