20 May
2009
20 May
'09
5:34 a.m.
Hi Henning,
Henning Westerholt schrieb:
you say that processing one INVITE needs 1:30 min?
This is way to slow
even with memory debugging. I regularly use this for debugging,
normally you should not notice a big difference in operation. Do you
get any "unusual" messages during the processing of the INVITE with
mem debug?
I can't see any unusal messages or errors (beside the fact, that I'm not
sure what is unusal ;-) ), but even startup is very slow. It needs
several minutes before we even see all kamailio processes in ps aux.
Here is one fragment of the startup logfile, where you can see, that
within one second not really much happens:
May 20 09:42:20 AmbriaSip1 kamailio: params (0x81677e0, 96), called from
route_struct.c: mk_action(106)
May 20 09:42:20 AmbriaSip1 kamailio: params (0x81677e0, 96), returns
address 0x81b3d9c frag. 0x81b3d84 (size=96) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 96), called from
route_struct.c: mk_action(106)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 96), returns
address 0x81b3e2c frag. 0x81b3e14 (size=96) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 96), called from
route_struct.c: mk_action(106)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 96), returns
address 0x81b3ebc frag. 0x81b3ea4 (size=96) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 3200), called
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 3200), returns
address 0x81b3f4c frag. 0x81b3f34 (size=3200) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params(0x81677e0, 0x81b3f4c),
called from socket_info.c: add_interfaces(411)
May 20 09:42:21 AmbriaSip1 kamailio: freeing frag. 0x81b3f34 alloc'ed
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 6400), called
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 6400), returns
address 0x81b4bfc frag. 0x81b4be4 (size=6400) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params(0x81677e0, 0x81b4bfc),
called from socket_info.c: add_interfaces(479)
May 20 09:42:21 AmbriaSip1 kamailio: freeing frag. 0x81b4be4 alloc'ed
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 3200), called
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 3200), returns
address 0x81b3f4c frag. 0x81b3f34 (size=3200) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params(0x81677e0, 0x81b3f4c),
called from socket_info.c: add_interfaces(411)
May 20 09:42:21 AmbriaSip1 kamailio: freeing frag. 0x81b3f34 alloc'ed
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 6400), called
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 6400), returns
address 0x81b4bfc frag. 0x81b4be4 (size=6400) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params(0x81677e0, 0x81b4bfc),
called from socket_info.c: add_interfaces(479)
May 20 09:42:21 AmbriaSip1 kamailio: freeing frag. 0x81b4be4 alloc'ed
from socket_info.c: add_interfaces(397)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 5), called from
socket_info.c: fix_socket_list(532)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 8), returns
address 0x81b3f4c frag. 0x81b3f34 (size=8) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 15), called from
socket_info.c: fix_socket_list(583)
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 16), returns
address 0x81b3f84 frag. 0x81b3f6c (size=16) on 1 -th hit
May 20 09:42:21 AmbriaSip1 kamailio: params (0x81677e0, 16), called from
name_alias.h: add_alias(99)
May 20 09:42:22 AmbriaSip1 kamailio: params (0x81677e0, 16), returns
address 0x81b3fc4 frag. 0x81b3fac (size=16) on 1 -th hit
May 20 09:42:22 AmbriaSip1 kamailio: params (0x81677e0, 11), called from
name_alias.h: add_alias(101)
May 20 09:42:22 AmbriaSip1 kamailio: params (0x81677e0, 12), returns
address 0x81b4004 frag. 0x81b3fec (size=12) on 1 -th hit
The logfile is full with this kind of messages.
The load of the machine (Xeon dualcore @3GHz) goes up to 2, but using
top we can't see that kamailio is using much CPU time (sometimes about
20%, but not more).
Regards,
Christian