Hello, optimizing for performances is a matter of configuration file. A special attention must be done to database and dns interactions.
Some tips for performances are collected in the next presentation: - http://www.kamailio.org/events/2015-Astricon/dcm-kamailio-surfing-big-waves-of-sip-with-style.pdf Cheers, Daniel On 12/01/16 09:00, Grant Bagdasarian wrote: > > Hello Daniel, > > > > I’ve enabled the debug only for a moment to get a better understanding > of Kamailio and what was happening under the hood. > > > > I’ve done some testing on a newer version of Kamailio (4.3) and didn’t > see this problem occur. So I’m not sure if it’s also software version > related. > > > > What else needs to be tuned except for the children parameter? > > Are there any guidelines/best practices in configuring the amount of > child parameters? > > > > Thanks for your answer! > > > > Regards, > > > > Grant > > > > *From:*sr-users [mailto:sr-users-boun...@lists.sip-router.org] *On > Behalf Of *Daniel-Constantin Mierla > *Sent:* Monday, January 11, 2016 5:37 PM > *To:* Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org> > *Subject:* Re: [SR-Users] siptrace retransmission's > > > > Hello, > > I expect that the log message from sip trace means that a > retransmission was detected and it is not going to be sent to > sipcature server. > > Printing the log messages for memory operations (malloc/free) is going > to be very costly in terms of performaces, be sure that parameters > memlog/memdbg are lower than debug. > > Also, depending of the config various tunings may be required for > increasing the perormances, such as value of children parameter. > > Cheers, > Daniel > > On 11/01/16 11:06, Grant Bagdasarian wrote: > > Hello All, > > > > I’m load testing Kamailio with siptrace (duplicate) enabled, but > for some reason not all SIP messages are arriving at the sip > capture server (kamailio instance with sipcapture). > > The load is an average of 50 CPS. > > > > I enabled debug 9 and I get the following messages. > > > > <core> [mem/q_malloc.c:369]: qm_malloc(): > qm_malloc(0x7fefde4da010, 1274) called from siptrace: siptrace.c: > trace_send_hep_duplicate(1615) > > <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, > 0x7fefde618a88), called from siptrace: siptrace.c: > trace_send_hep_duplicate(1659) > > <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, > 0x7fefde61ee18), called from siptrace: siptrace.c: > trace_send_hep_duplicate(1660) > > <core> [mem/q_malloc.c:474]: qm_free(): qm_free: freeing frag. > 0x7fefde61ede8 alloc'ed from siptrace: siptrace.c: > trace_send_hep_duplicate(1615) > > <core> [mem/q_malloc.c:369]: qm_malloc(): > qm_malloc(0x7fefde4da010, 1271) called from siptrace: siptrace.c: > trace_send_hep_duplicate(1615) > > <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, > 0x7fefde61b488), called from siptrace: siptrace.c: > trace_send_hep_duplicate(1659) > > <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, > 0x7fefde61e880), called from siptrace: siptrace.c: > trace_send_hep_duplicate(1660) > > <core> [mem/q_malloc.c:474]: qm_free(): qm_free: freeing frag. > 0x7fefde61e850 alloc'ed from siptrace: siptrace.c: > trace_send_hep_duplicate(1615) > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission > > > > In siptrace.c I see the following line of code: > > > > if(ps->flags&TMCB_RETR_F) { > > LM_DBG("retransmission\n"); > > return; > > } > > > > Does this in fact retransmit the message to the capture server? > > Has anyone else load tested kamailio with siptrace on? > > > > I’m using Kamailio 4.1. I’m also using the setflag(..) function in > siptrace module to duplicate all forwarded messages to the capture > server. > > > > Regards, > > > > Grant > > > > > _______________________________________________ > > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > > sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> > > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > Daniel-Constantin Mierla > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - > http://www.linkedin.com/in/miconda > Book: SIP Routing With Kamailio - http://www.asipto.com > http://miconda.eu -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users