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

ILYA Khlopotov ilya.khlopotov@REDACTED
Tue Oct 31 23:19:48 CET 2017

config as module approach is also used in CouchDB plugin system here

On October 28, 2017 12:39:07 AM PDT, Benoit Chesneau <bchesneau@REDACTED> wrote:
>> 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
>erlang-questions mailing list

Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171031/3d238fdc/attachment.htm>

More information about the erlang-questions mailing list