Both hash size and timer interval are configurable so the admin can tune them
to fit their needs.
One reason for having a hash is to avoid running over all records when the
timer fires.
When the timer fires, the modules checks only one entry into the hash table,
that's why the timer_interval is divided by reg_hsize during initialization.
If you want to use expire=120 with a hash_size =4, then set:
modparam("uac_registrant", "timer_interval", 32)
modparam("uac_registrant", "hash_size", 4)
This will result in 16 branches in the hash table. Each record will be checked
every 32s and every 2s the timer will fire checking one branch in the hash
table.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43646676_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
