Go to file
Damian Gryski 74a9798053 more TODOs
2018-08-09 09:49:14 -07:00
performance-ptbr.md [PT-BR] Add introduction and 'When and Where to Optimize' sections. WIP #17 2018-05-02 12:57:34 -07:00
performance-zh.md -Synchronize English version changes 2018-04-10 18:32:35 +08:00
performance.md more TODOs 2018-08-09 09:49:14 -07:00
README.md optimize for front-end conversion 2018-03-13 20:40:49 -07:00
TODO benchmarking talk 2018-04-11 23:55:10 -07:00

go-perfbook

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

Contributing

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.