6 Apr
2013
6 Apr
'13
1:58 p.m.
On 4/6/13 12:32 PM, Juha Heinanen wrote:
Hugh Waite writes:
keeping different
indexes will add lot of complexity in synchronizing
them on insert/update/delete, which can end up also in loss of
performances. Other field that would need indexes are contact address,
callid, path, if you look at the other types of lookups done in usrloc.
The aor is not necessary to be kept in order to locate the record,
aorhash would be enough (which is unsigned int) along with ruid. Getting
aorhash from aor is really fast, so keeping only the aor might be better
in some situations when it is needed for other purposes.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
The usrloc tables are indexed on the hash of the
AoR, so one is needed
to find the correct entry.
ok, but why cannot a new index on ruid field be created
in which case
unregister would not need uri (aor) or use argument at all?