Skip to content

About

Evidence-driven Go performance engineering with docs, Agent Skill, benchmarks, and reproducible optimization proofs.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Latest commit

 

History

26 Commits

Folders and files

Repository files navigation

Go Performance Engineering

English | 简体中文

Evidence-driven Go performance engineering with documentation, Agent Skill, and reproducible proofs.

Overview

This repository focuses on understanding and improving Go performance through evidence.

It is not a collection of isolated optimization tricks.

The project covers:

  • compiler and SSA optimization;
  • CPU cache and memory layout;
  • concurrency and synchronization;
  • allocation and garbage collection;
  • unsafe and runtime boundaries;
  • benchmarking and profiling methodology.

Repository Structure

.
├── docs/
│   Complete performance engineering documentation
│
├── skill/
│   Agent Skill package
│
└── proofs/
    Minimal reproducible experiments

Documentation

The docs/ directory contains the complete knowledge base.

Start here:

Agent Skill

The skill/ directory contains the AI-oriented performance workflow.

It provides:

  • diagnostic routing;
  • evidence requirements;
  • optimization risk rules;
  • maintainability checks;
  • validation workflow.

Start here:

Proofs

The proofs/ directory contains minimal experiments for specific performance behaviors.

A proof demonstrates:

This mechanism exists and can be reproduced under documented conditions.

It does not claim:

This optimization is always faster.

See:

Articles & Case Studies

Articles published on Gopher Atlas connect Go performance concepts with reproducible experiments and documented evidence. Both English and Simplified Chinese editions are available.

Study Articles Reproducible evidence
Slice Retention — How a 100-byte slice can keep a 100 MiB backing array alive English · 简体中文 Proof · Windows report · Linux report
Heap Ballast (Historical) — The mechanism and evolution of a classic Go GC tuning technique English · 简体中文 Proof · Windows report · Linux report
Bounds Check Elimination — How the compiler proves redundant slice bounds checks English · 简体中文 Proof · Windows report · Linux report

The experiments establish specific mechanisms under recorded conditions, not universal performance gains. Historical techniques are preserved for study and reproducibility, not as default recommendations for modern Go applications.

Philosophy

Measure
  ↓
Understand the cost model
  ↓
Make the smallest justified change
  ↓
Benchmark
  ↓
Validate system impact
  ↓
Preserve the reason for the optimization

License

Apache License 2.0

About

Evidence-driven Go performance engineering with docs, Agent Skill, benchmarks, and reproducible optimization proofs.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages