Hello,
setting the hash size to 32MB is way too much, are you having like 100
000 000 active calls at the same time?
The size of the hash is used for computing the number of slots in the
hash table, not the capacity in terms of memory size of all items stored
in hash table.
Cheers,
Daniel
On 03/02/14 07:33, Shankar wrote:
Hi Alex,
We set the hash size to 32 MB and found that the hash size is not the
same as configured one. At the max it was taking 64KB.
Regards,
Shankar
Date: Mon, 03 Feb 2014 00:27:29 -0500
From: Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>>
To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] Regd. MAX_LDG_LOCKS
Message-ID: <52EF28C1.5010204(a)evaristesys.com
<mailto:52EF28C1.5010204@evaristesys.com>>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 02/03/2014 12:22 AM, Shankar wrote:
Also we found that in ?dialog.c? the variable
dlg_hash_size should be
?unsigned int?. Hope this will be taken care in
next release of
Kamailio.
How did you arrive at that conclusion?
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web:
http://www.evaristesys.com/,
http://www.alexbalashov.com/
*From:*Shankar [mailto:shankar.rk@plintron.com]
*Sent:* Monday, February 03, 2014 10:53 AM
*To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List'
*Subject:* Regd. MAX_LDG_LOCKS
Hello,
Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c?
Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if
the hash size is increased?
Also we found that in ‘dialog.c’ the variable dlg_hash_size should be
‘unsigned int’. Hope this will be taken care in next release of Kamailio.
Regards,
Shankar
_______________________________________________
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