[erlang-questions] OpenSSL 1.0.X : SSL_MODE_RELEASE_BUFFERS

Morgan Segalis <>
Sun May 27 23:16:39 CEST 2012


After checking out,

"process_info(spawn(Fun), memory)."

return the value in bits… so each process should take 2KB, this is where I do not understand where all this memory is taken…


Le 27 mai 2012 à 19:49, Morgan Segalis a écrit :

> Hi Antoine,
> 
> I guess I have been mislead by ejabberd which can activate the option when available, but after investigating, it seems that they have done connection handling through a C-node using openssl.
> 
> Then from where can come this "huge" memory footprint, is there a way in Erlang to check from where memory request are coming ?
> Because when I check with "process_info(spawn(Fun), memory)."
> 
> Here's what I get :
> 
> before gc: {memory,13376}          
> after gc: {memory,2108} 
> 
> for each client…
> 2108 is that word size, or bits ? How can I get word size ? My system is 64bits, so word size is also ?
> 
> Thanks,
> 
> Morgan.
> 
> Le 27 mai 2012 à 16:39, Antoine Koener a écrit :
> 
>> Hi, Afaik
>> OpenSSL is only used in ssl for the crypto module. So buffers may not
>> be relates with your issue...
>> 
>> --
>> Was on the go
>> 
>> On 27 mai 2012, at 14:20, Morgan Segalis <> wrote:
>> 
>>> Hi everyone,
>>> 
>>> Since a month or so, I'm looking for ways to reduce SSL memory footprint, in vain…
>>> 
>>> - I have read something about SSL_MODE_RELEASE_BUFFERS which can help you save some memory for idles connections (around 45Ko).
>>> Since most of client connected are idle for a long time, I was thinking that would be a way to go.
>>> 
>>> I'm wondering if Erlang R15B can work with openssl's version 1.0.X, and if so, how to active this option ?
>>> 
>>> Thanks,
>>> 
>>> Morgan.
>>> _______________________________________________
>>> erlang-questions mailing list
>>> 
>>> http://erlang.org/mailman/listinfo/erlang-questions
> 




More information about the erlang-questions mailing list