Go Performance Testing

SkillDocs & knowledge

Design, run, compare, and interpret Go performance evidence using benchmarks, B.Loop, benchstat, pprof, traces, escape analysis, cache locality, false sharing, sync.Pool, GC limits, container CPU behavior, and PGO. Use when investigating Go latency, throughput, CPU, memory, allocations, contention, runtime behavior, performance regressions, or optimization claims.

Use Go Performance Testing in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Go Performance Testing and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Go Performance Testing skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Go Performance TestingStart free

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/LVTD-LLC/skills/skills/go-performance-testing/SKILL.md and read by Ahel’s review.

Optimize only after establishing a representative, repeatable measurement and a specific hypothesis.

Core Workflow

Define the user-visible metric and representative workload.
Stabilize correctness before measuring performance.
Write focused benchmarks with realistic inputs and controlled setup.
Collect repeated baseline samples in comparable conditions.
Use allocations, profiles, and traces to form a causal hypothesis.
Make one bounded change.
Compare repeated before/after samples statistically.
Recheck correctness and the end-to-end workload.

Guardrails

Do not optimize from one benchmark line or an unrepresentative microbenchmark.
Do not compare runs made under materially different environments.
Do not treat coverage or race detection as performance evidence.
Name the profile sample type and distinguish flat from cumulative cost.
Prefer B.Loop only when the pinned Go version supports it.
Keep production profile endpoints protected and operationally controlled.
Do not encode cache-line size, escape output, or inliner budgets as portable facts.
Do not use sync.Pool as a cache or resource owner.

Source Notes

Guidance is transformed and paraphrased from Inanc Gumus, Go by Example: Programmer's Guide to Idiomatic and Testable Programs (Manning, 2025), especially Chapter 3. Examples are original.

Diagnostics, locality, allocation, GC, and container guidance also incorporates transformed material from Teiva Harsanyi, 100 Go Mistakes and How to Avoid Them (Manning, 2022), Chapter 12.

Book: https://www.manning.com/books/go-by-example

Verify current behavior against https://pkg.go.dev/testing, https://go.dev/doc/diagnostics, and https://go.dev/doc/pgo.

Signals

GitHub stars: 1k
Forks: 316
Last commit: Oct 2026

Advanced

Item type: skill
Key: go-performance-testing
Source: github.com/hashgraph-online/awesome-codex-plugins

github.com/hashgraph-online/awesome-codex-plugins

Task	Load
Benchmark a function or package	`guidelines.md`, `workflows/benchmark-code.md`
Investigate a regression	`workflows/investigate-performance.md`
Evaluate profile-guided optimization	`workflows/evaluate-pgo.md`
Choose benchmark and profile controls	`references/performance-testing/rules.md`
Interpret metrics and profiles	`references/performance-testing/knowledge.md`
Review benchmark patterns	`references/performance-testing/examples.md`