Get the latest tech news
A 40ms Go garbage collector pause caused by swap
C pause caused by swap I’m writing this so you don’t slap your forehead like I almost did when I decided to run swap in production to absorb memory spikes. I had a cgroup with two processes: one is a Go process that calls io.ReadAll and then proto.Unmarshal, creating a blob and then a graph struct (which is marked as scan by Go’s allocator).
None
Or read this on Hacker News