[rdtsc]

> irrelevant in Erlang world

Exactly. That is a subtle distinction but for cases where responsiveness and low latency is important that is key. Another thing Erlang has is isolation of process heaps. If one process crashes, it won't affect others. No shared data structures between processes. It all goes to fault tolerance but also a major win for a completely concurrent garbage collection.

[masklinn]

> If one process crashes, it won't affect others.

Unless they're linking or monitoring one another, an other important property of tolerant and distributed system.

[rdtsc]

But that is on purpose. Sometimes you do want that. In other words they are explicitly set up to monitor/link each other.

[masklinn]

> But that is on purpose.

Indeed, but I was pointing it out because it's important to be able to do it.