Dave Cheney • 1/5/2021

A few bytes here, a few there, pretty soon you’re talking real memory

This technical article analyzes a Go benchmark where `sort.Strings` causes an unexpected heap allocation per iteration. It explains the reason through Go's interface implementation (a two-word structure) and how assigning a slice to an interface leads to indirection and escape to the heap. The post includes code examples, compiler insights, and profiling output, making it a deep dive into Go memory behavior for developers.

0 comments

#benchmarking #go #interfaces