19 Mar
2012
19 Mar
'12
10:49 a.m.
On Mon, Mar 19, 2012 at 05:31, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
Hello,
On 3/19/12 10:03 AM, Juha Heinanen wrote:
That may be the reason why it consumes so much memory. The custom
memory manager is not exactly memory efficient, it trades speed for
efficiency.
-Jan
Daniel-Constantin Mierla writes:
afaik, the ca_list is loaded by libssl internally. Kamailio just sets custom
memory manager and gives the path to ca_list. is this with default mem size?
i would just like to add that once i increased shared memory from
32m to 64m, sip proxy started, but only about 10M was left as free: Shared Memory
free_size 8510256
max_used_size 58623504
real_used_size 58598608
total_size 67108864
it means that debian's ca_list consumes more than 20M of shared memory,
which seems like a lot for 139 entries.
Is this by one ca_list only, or do you have many tls domains, each with own
profile?
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users