[ejabberd] Ejabberd Memory Consumption (SSL & Compression)

William Key williamkey at gmail.com
Sat Mar 5 21:19:33 MSK 2011


We're running v0.9.8k. What version of Ejabberd has the updated TLS code?

On Sat, Mar 5, 2011 at 4:41 AM, Evgeniy Khramtsov <xramtsov at gmail.com>wrote:

> 05.03.2011 16:02, Chris Moos wrote:
>
>>
>> Hi,
>>
>> I noticed that in OpenSSL 1.0.0 there is the following change:
>>
>> *) New option SSL_OP_NO_COMP to disable use of compression selectively
>>      in SSL structures. New SSL ctrl to set maximum send fragment size.
>>      Save memory by seeting the I/O buffer sizes dynamically instead of
>>      using the maximum available value.
>>      [Steve Henson]
>>
>> Any idea how much overhead the compression structures add?
>>
>>
>
> Indeed, how much? :)
>
>
> --
> Regards,
> Evgeniy Khramtsov, ProcessOne.
> xmpp:xram at jabber.ru.
>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20110305/c16aa1e4/attachment.html>


More information about the ejabberd mailing list