[erlang-questions] sharing config via a dynamically compiled module?

Benoit Chesneau bchesneau@REDACTED
Sat Oct 28 09:39:07 CEST 2017


> On 28 Oct 2017, at 08:38, Max Lapshin <max.lapshin@REDACTED> wrote:
> 
> Take a look at thread nearby.
> 
> > All literals belong to a loaded module instance. When that (old) module instance is purged, all process heaps are scanned and heaps containing those literals will do a special garbage collection where the literals are copied.
> 
> Each config change may lead to rescanning heaps of all processes.
> 
> 
> Frankly speaking global ets is much easier =)
> 


Right. One another advantage to ETS i that you can store any terms even refs where it's not possible . At the cost of increasing the number of ETS tables used though...

- benoƮt


More information about the erlang-questions mailing list