if you set memjoin to 0, do you see any difference?

Can you try again (with memjoin 1 as well as 0) and send the output of:

kamctl mi get_statistics shmem:

before executing the reload commands?

When it gets to 100%, can you see which process is using the cpu and attach to it with:

gdb /path/to/kamailio PID

then do:

bt full

and send output here?


On 11/18/12 4:09 PM, Uri Shacked wrote:
After some testing I notice the following:
First reload of 5 million records after kamailio started took about 9 sec.
Second reload (4 minutes after the first one) took 60 sec.
The third one (again about 4 minutes after the secind) got kamailio to use 100% cpu and after 13 minutes! i killed it.....
I can understand that the memory manger works harder, still, any ideas on how to use mem_join and keep on reloading data.
(in real life our data loads 5 million records once a day when almost no traffic. still after a few days it stops...)

On Sun, Nov 18, 2012 at 11:52 AM, Uri Shacked <ushacked@gmail.com> wrote:


I am using MTREE and DIALPLAN modules to load lots of info to kamailio. (6 million rows).

When kamailio was running with 3.2.1 (no mem_join=1 option), the used size was increasing but the process of loading the data was fast eanough.

I upgraded to 3.3.2 and set mem_join=1. Now the loading process take about 10 time longer and sometimes stops kamailio from responding to traffic.

Any ideas?



SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda