Thoughts on Go performance optimization
Switch branches/tags
Nothing to show
Clone or download
seebs and dgryski Minor typo fixes
Added a comma to one sentence, otherwise this is markdown
issues (escape a _, match a backtick) and a couple of spellings
of "contended" as "contented". (I hope that one isn't
to contentious, but I contend that the content isn't
changed and I'm content with it, also English is a mistake.)
Latest commit 2b24ff3 Sep 27, 2018


Buy Me A Coffee

This document outlines best practices for writing high-performance Go code.

The first sections cover writing optimized code in any language. The later sections cover Go-specific techniques.

Multiple Language Versions

Table of Contents

  1. Writing and Optimizing Go code
  2. How to Optimize
    1. Optimization Workflow
    2. Concrete Optimization Tips
    3. Optimization Workflow Summary
  3. Data Changes
  4. Algorithmic Changes
  5. Benchmark Inputs
  6. Program Tuning
  7. Tooling
    1. Profiling
    2. Tracer
  8. Garbage Collection
  9. Runtime and Compiler
  10. Unsafe
  11. Common gotchas with the standard library
  12. Alternate Implementations
  13. CGO
  14. Advanced Techniques
  15. Assembly
  16. Optimizing an Entire Service
  17. Appendix
    1. Implementing Research Papers


This is a work-in-progress book in Go performance.

There are different ways to contribute:

  1. add to or summarizes the resources in TODO
  2. add bullet points or new topics to be covered
  3. write prose and flesh out the sections in the book

Eventually sample programs to optimize and exercises will be needed (maybe).

Coordination will be done in the #performance channel on the Gophers slack.