Go runtime garbage collector

An engineer has documented a case where a Go application suffered a 40-millisecond garbage collector pause, traced back not to the runtime itself but to swap activity on the host. When the Go runtime's memory pages get swapped to disk, the GC must touch them, forcing the kernel to page them back in and inflating stop-the-world pauses. The writeup is drawing attention among developers who assumed Go's GC pauses were reliably sub-millisecond.