In Erjang, every node runs on a single heap, and so global gc will sometimes happen. On the other hand, Erjang does not copy messages between processes — they a

In Erjang, every node runs on a single heap, and so global gc will sometimes happen. On the other hand, Erjang does not copy messages between processes — they are simply shared, and so that might leave some room for savings. Will be interesting to see what happens, no doubt. Message copying will have to be implemented, anyway, for inter-node communication. I don’t know how Java’s various garbage collector compares to the one in Erlang, but I guess that Java’s is significantly faster. Doubtful. A garbage collector specially designed for small heaps, running on such, will outperform Java's general-purpose ones. Also, Erlang's GC is stop-the-world (where "world" here is an Erlang process), and that yields numerous benefits. I think Java's GC will not be better for erjang.