On Mon, Dec 04, 2017 at 03:28:08PM -0500, Mark Blackford wrote:
> So, it sounds like from what you describe, I will set my hash size to
> be a few times larger than my forecasted profile size to keep matching
> operations to a minimal. And since dialogs timeout anyway if they are
> not cleared
Hi Daniel,
Thanks for your responses. This discussion has been very useful.
Our code is along the lines that you suggest in which we are using some
database ops prior to the dialog calls to gather if the user is call
limited and if so, the provisioned users "max calls allowed" per billing
The hash_size has no relevance on how many dialogs can be handled. It is
only related to the lookup performance. So even with hash_size=1 you can
have same number of dialogs as with hash_size=4096 or higher.
The difference is that with hash_size=1, all the dialogs are in a single
linked list, so
Thank you for your response!
I am currently replacing the call_control module used with CDRTool Prepaid
with the dialog module using hash tables. The speed and stability are
tremendously better!
My concern is two-fold:
1) I do not want calls to be blocked because I set the hash table size too
Hello,
hash size does not set any limitation to the number of dialogs (active
calls), it has impact on searching the dialogs, so if you have a lot of
active calls, increasing the hash size might improve performances.
Effectively the hash size is used to compute the number of slots (aka
buckets)
