How the Erlang get soft-realtime with GC?

Question

Generally GC is not a good choice to get a soft real-time attribute. But Erlang is GC based language can be soft real-time.

Does it mean Erlang have almost no GC latency? How does it work?

Even the hard real-time garbage collectors exists. E.g., lambda-the-ultimate.org/node/2393

Waquo · Accepted Answer · 2012-04-24 15:19:56Z

up vote 7 down vote accepted

Erlang processes don't share memory, each one has its own heap and they can be garbage-collected independently.

Many small heaps result in many small GC-pauses, rather than few big ones.

answered Apr 24 '12 at 15:19

Waquo
1,391510

Here's great write-up on Erlang's GC (which includes your point and makes a few others): prog21.dadgum.com/16.html – scvalex Aug 5 '12 at 1:27

1 Answer