News for hackers. Stuff that matters.
Re:Iterative Optimization on Hot Paths in Go Apps by berfarah on Friday October 05, 2018 @04:23PM (#18151419)
(author here)

Good question! Because this is on a hot code path, we were allocating new values faster than the garbage collector was able to remove them. Over extended periods of time, the server would trend toward running out of memory.

Re:Iterative Optimization on Hot Paths in Go Apps by blaisio on Friday October 05, 2018 @06:11PM (#18152150)
Interesting! That sounds like a garbage collector bug! It's probably worth opening a ticket.