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?
erlanggarbage-collectionreal time
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?
Best Answer
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.