How to Interpret Benchmark Results in Go

Interpret Go benchmark results by focusing on the ns/op (nanoseconds per operation) for speed, B/op (bytes allocated per operation) for memory pressure, and allocs/op (allocations per operation) for garbage collection overhead. Run benchmarks with go test -bench=. -benchmem to see these metrics, where lower values indicate better performance.

go test -bench=. -benchmem ./mypackage

The output shows ns/op as the average time per iteration, B/op as the average bytes allocated, and allocs/op as the average number of heap allocations. A result like 100 ns/op 0 B/op 0 allocs/op is faster and more efficient than 200 ns/op 128 B/op 2 allocs/op.

Benchmark results tell you how fast your code runs and how much memory it uses. The first number is how long each operation takes, while the other two numbers show how much memory is created and how often. Lower numbers are always better because they mean your code is faster and uses less memory.