[erlang-questions] Erlang code loading

CGS cgsmcmlxxv@REDACTED
Mon Nov 21 12:50:01 CET 2011


One instance per process, one memory allocation per process (even if it 
is the same code running). Erlang has no explicit knowledge of beam 
shared objects as far as I know. If somebody knows differently, please, 
correct me.

CGS




On 11/21/2011 12:40 PM, Max Bourinov wrote:
> Thank you for your reply! But in Erlang processes, not threads. There 
> are some differences between them...
>
>
>
> Отправлено с iPhone
>
> 21.11.2011, в 15:05, CGS <cgsmcmlxxv@REDACTED 
> <mailto:cgsmcmlxxv@REDACTED>> написал(а):
>
>> Hi, Max,
>>
>> Not an expert, but I think the memory is multiplied by the number of 
>> threads. Meaning, you start with an initial heap for that thread and 
>> add to that the states and other internal variables (repeat that for 
>> all the threads). At least that I noticed from my codes by now. If I 
>> am wrong, I apologize.
>>
>> Cheers,
>> CGS
>>
>>
>>
>>
>> On 11/21/2011 11:57 AM, Max Bourinov wrote:
>>> Hi Erlangers,
>>>
>>> I am wondering how my Erlang app would behave in this case:
>>>
>>> I have a lot identical processes (the same module, state of couse is 
>>> different in each process). The module that I swap many times has a 
>>> huge function. I want to clarify how much memory it will take? It 
>>> will take memory for that huge function in each process or only once?
>>>
>>> I believe it will take memory only once, but I want to make sure.
>>>
>>> Best regards,
>>> Max
>>>
>>>
>>>
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
>> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111121/64a669af/attachment.htm>


More information about the erlang-questions mailing list