<html><head></head><body>config as module approach is also used in CouchDB plugin system here<br>
<a href="https://github.com/apache/couchdb/blob/master/src/couch_epi/src/couch_epi_data_gen.erl">https://github.com/apache/couchdb/blob/master/src/couch_epi/src/couch_epi_data_gen.erl</a><br><br><div class="gmail_quote">On October 28, 2017 12:39:07 AM PDT, Benoit Chesneau <bchesneau@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On 28 Oct 2017, at 08:38, Max Lapshin <max.lapshin@gmail.com> wrote:<br /> <br /> Take a look at thread nearby.<br /> <br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> 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.<br /></blockquote> <br /> Each config change may lead to rescanning heaps of all processes.<br /> <br /> <br /> Frankly speaking global ets is much easier =)<br /> <br /></blockquote><br /><br />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...<br
/><br />- benoît<br /><hr /><br />erlang-questions mailing list<br />erlang-questions@erlang.org<br /><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>