[sr-dev] nat keepalive partitioning in usrloc db only mode

Daniel-Constantin Mierla miconda at gmail.com
Wed May 6 22:20:16 CEST 2015



On 06/05/15 21:20, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> I think this is a fix and still ok to apply in this testing phase. There
>> is no new feature comparing with previous stable, but making it be the
>> same in functionality. However, I wanted to check with all devs and see
>> other opinions. And again, it is only about db_mode=DB_ONLY for
>> usrloc.
> what is the performance impact of this compared to the present raw query
> implementation that fetches id modulo x from location table?

It allows to make clear indexes (no bitwise and no module operations in
match expression), that speeds up a lot. Anyhow, the main issue was that
the old implementation was working for mysql (and perhaps postgress) only.

>
> also, is there any performance implications on normal lookups and saves
> in db only mode?
lookup is not affected at all. update of existing record is not affected
as well. first registration (insert) will set an extra column with
integer value.

Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com




More information about the sr-dev mailing list