Why can a Go service be OOM-killed while its heap looks healthy?

The heap is only part of the container's memory usage. Goroutine stacks, native allocations, and runtime overhead also count toward the container limit.

In this new article from Gulcan, you will learn:

- How CPU quotas affect Go's parallelism and why extra threads can increase throttling.
- How to measure total container memory, including goroutine stacks and native allocations.
- Why a tighter memory budget can increase garbage collection work and reduce throughput.

Read: https://learnkube.com/go-kubernetes-requests-limits

This article is also included in our book on Kubernetes rightsizing: https://learnkube.com/kubernetes-rightsizing