4 ms·
Erlang has micro-heaps, each process has its own heap so GC pause times are minuscule. Having too much address space is a liability, so limiting the reach of p
by sitkack 12y ago
Erlang has micro-heaps, each process has its own heap so GC pause times are minuscule. Having too much address space is a liability, so limiting the reach of piece of code has GC advantages. I think as memory limits increase we will move to something like tagged heaps, a melding of GC, memory regions and static allocation. One can already get this by running multiple emscripten compiled programs in a JS engine, esp if one pushes tasks into web workers.
You don't necessarily have to serialize data between services if one uses something like capnproto or flat buffers.
Why have one heap?
- nickik 12y agoThat kind of architecture might be ok for problems but I not sure how general it is. Also, why force a diffrent programming model when it is possible to have a GC that does a good job. There is erlang on java and it performs quite well, so you can combine the two things. I dont want technogoly to force my architecture, if I make a choice to go with actors I want it to be, because its the right choice and not because I have to.
- sitkack 12y agoHaving a global flat address space has its tradeoffs. We use a GC because we don't want to have to specify the lifetime of memory ourselves. Rust also has no false sharing between threads, much like Erlang, a thread always owns the memory it operates on. Technology always forces architecture.
- dbaupp 12y agoRust does allow shared memory, either via unsafe code, or using a safe wrapper provided by the standard library (or an external library). http://doc.rust-lang.org/nightly/std/sync/struct.Arc.html http://doc.rust-lang.org/nightly/std/sync/struct.Arc.html