News for hackers. Stuff that matters.
Re:Go GC: Solving the Latency Problem in Go 1.5 by davidw on Wednesday July 08, 2015 @05:42PM (#9854791)
Erlang's per-process (Erlang process, not Unix process) GC is pretty good from this point of view. I'm surprised they didn't mention it as something to think about.
Re:Go GC: Solving the Latency Problem in Go 1.5 by andrewchambers on Wednesday July 08, 2015 @06:37PM (#9855077)
Why would you mention it? Go is shares all memory, erlang doesn't. It is a different problem.
Re:Go GC: Solving the Latency Problem in Go 1.5 by jzelinskie on Wednesday July 08, 2015 @09:53PM (#9855781)
Actually, IIRC Erlang does have a shared heap, but it is used as an optimization to avoid copying very large objects.
Re:Go GC: Solving the Latency Problem in Go 1.5 by andrewchambers on Wednesday July 08, 2015 @10:46PM (#9855916)
That doesn't contradict what I said. Go shares ALL memory, erlang may share some sometimes.
Re:Go GC: Solving the Latency Problem in Go 1.5 by stcredzero on Wednesday July 08, 2015 @05:48PM (#9854820)
I've gone through the exercise of enabling something like per-process GC in Go by using multiple processes and the standard Go RPC library. It's easier to get to that point in Erlang, because you're already there by default.

Very good low-latency GC is good an alternative to per-process GC, especially combined with Go's ability to let you write to avoid GC pressure.