They addressed this in the article: > These latency spikes definitely smelled like garbage collection performance impact, but we had written the Go code very e

They addressed this in the article: > These latency spikes definitely smelled like garbage collection performance impact, but we had written the Go code very efficiently and had very few allocations. We were not creating a lot of garbage. The problem was due to the GC scanning all of their allocated memory and taking a long time to do so, regardless of it all being necessary and valid memory usage.