[erlang-questions] Erlang Garbage Collection

[orbitz@REDACTED]

The very basics are Erlang either has a per-process heap, so any data  
the process uses is kept in its specific heap, or a hybrid heap which  
has a per-process and global heap for shared data.

The issue with the former is you can have a lot of duplicated data if  
processes are sharing a lot.
The benefit is cleaning up after a process is as simple as destroying  
its heap

The issue with the latter is your GC algorithm has to do more work  
when it is cleaning out the global heap.
The benefit is you are duplicating less data.

This is how things worked a year or so ago AFAIK.

I would imagine, but do not know, that the semantics of erlang might  
make gc'ing a bit easier.  For instance you don't have to worry about  
cycle.

Hopefully someone will have a bit more detail than myself.

On Mar 19, 2008, at 8:34 PM, Mark Mzyk wrote:

> Hey Everyone,
>
> I've recently finished reading several articles on garbage  
> collection in general and a bit on garbage collection in Java.  I  
> was curious if any one knows how Erlang garbage collection works,  
> or where I could potentially find out?  I'm especially curious if  
> Erlang, with it's focus on concurrency, has an special garbage  
> collection issues it has to deal with.
>
> Thanks,
>
> Mark Mzyk
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions