3 ms·
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 ab
by davidw 11y ago
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.
- stcredzero 11y agoI'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.
- andrewchambers 11y agoWhy would you mention it? Go is shares all memory, erlang doesn't. It is a different problem.
- jzelinskie 11y agoActually, IIRC Erlang does have a shared heap, but it is used as an optimization to avoid copying very large objects.
- andrewchambers 11y agoThat doesn't contradict what I said. Go shares ALL memory, erlang may share some sometimes.