[erlang-questions] Erlang and Memory management

[Tim Watson]

> Probably most Erlang code would faster with a shared heap, but some code
> might slow down -- maybe by a lot. Putting certain smarts in Send might
> help: e.g., if the receiving process isn't ready to run, copy; if it is
> ready, just pass the pointer to shared memory. I'm sure lots more strategies
> might be devised. And I'm about equally sure they'll all have their own
> limits and pitfalls.

Indeed. This is why the JVM provides a number of different
(configurable) GC strategies, and does quite a lot of "self tuning"
where applicable.