Book Image

Hands-On High Performance with Go

By : Bob Strecansky
Book Image

Hands-On High Performance with Go

By: Bob Strecansky

Overview of this book

Go is an easy-to-write language that is popular among developers thanks to its features such as concurrency, portability, and ability to reduce complexity. This Golang book will teach you how to construct idiomatic Go code that is reusable and highly performant. Starting with an introduction to performance concepts, you’ll understand the ideology behind Go’s performance. You’ll then learn how to effectively implement Go data structures and algorithms along with exploring data manipulation and organization to write programs for scalable software. This book covers channels and goroutines for parallelism and concurrency to write high-performance code for distributed systems. As you advance, you’ll learn how to manage memory effectively. You’ll explore the compute unified device architecture (CUDA) application programming interface (API), use containers to build Go code, and work with the Go build cache for quicker compilation. You’ll also get to grips with profiling and tracing Go code for detecting bottlenecks in your system. Finally, you’ll evaluate clusters and job queues for performance optimization and monitor the application for performance regression. By the end of this Go programming book, you’ll be able to improve existing code and fulfill customer requirements by writing efficient programs.
Table of Contents (20 chapters)
Section 1: Learning about Performance in Go
Section 2: Applying Performance Concepts in Go
Section 3: Deploying, Monitoring, and Iterating on Go Programs with Performance in Mind

Interpreting flame graphs within pprof

One of the most helpful/useful tools in the upstream pprof package is the flame graph. A flame graph is a fixed-rate sampling visualization that can help to determine hot codepaths in a profile. As your programs get more and more complex, the profiles become larger and larger. It will often become difficult to know exactly what codepath is eating up the most CPU, or, as I often like to call it, the long pole in the tent.

Flame graphs were originally developed by Brendan Gregg at Netflix to solve a MySQL CPU utilization problem. The advent of this visualization has helped many programmers and system administrators determine what the source of latency is in their program. The pprof binary produces an icicle-style (flames pointing downward) flame graph. In a flame graph, we have data visualized in a specific frame:

  • The x axis is the collection...