[OpenSIPS-Users] Opensips debug logging performance impact

Liviu Chircu liviu at opensips.org
Tue May 15 02:03:40 EDT 2018

Hi Rajesh,

The only overhead added by "log_level = 4" are the extra logs 
themselves. And, yes, DEBUG mode is quite verbose and could lead to a 
lot of output, easily filling up entire GB within just a few hours.

As with all such questions, the only correct answer is: "it depends". 
For example:

* are you logging to an SSD?
* how many CPS do you throw at OpenSIPS?
* how much scripting logic do you have?
* have you enabled async logging in your syslog OpenSIPS log?
* are there any other applications which are heavily logging to the same 

You should perform some tests before enabling "log_level = 4" on a 
CPS-heavy OpenSIPS deployment. The best advice is to monitor the 
"Recv-Q" field of "netstat -tlnp" for your OpenSIPS TCP listeners, and 
check if SIP messages are either piling up or getting processed 
immediately as they arrive.

Best regards,

Liviu Chircu
OpenSIPS Developer

On 08.05.2018 21:54, Govindaraj, Rajesh wrote:
> Hi,
> To debug an issue related to udp send failed, opensips was run in 
> debug level 5 in version 1.11.5.
> We found that opensips performance went down. At a particular time, 
> the thread were blocked for 3-4 seconds while trying to send tcp 
> messages. On code browsing doesn’t look like opensips is waiting for 
> something and delay is purely happening because opensips thread was 
> not scheduled.
> We analysed for any increase in load for opensips around this time but 
> could not find any significant increase in input load.
> Just wanted co-members advise, does debug logging slow down opensips 
> to such an extend where message processing delays are so much that 
> keep alives fail and noticeable impact happens?
> Please advise.
> Thanks,
> *Rajeshkumar Govindaraj*
> Software Engineer
> 777 Commerce Drive,
> Fairfield, CT-06825
> *T*+1 201 253 7803 |*M* +1 475 439 9918 |*E* Rajesh.Govindaraj at ipc.com 
> <mailto:Rajesh.Govindaraj at ipc.com>
> Follow us on twitter: @ipc_Systems_Inc www.ipc.com <http://www.ipc.com/>
> cid:image006.jpg at 01D1940F.3E021840
> DISCLAIMER: This e-mail may contain information that is confidential, 
> privileged or otherwise protected from disclosure. If you are not an 
> intended recipient of this e-mail, do not duplicate or redistribute it 
> by any means. Please delete it and any attachments and notify the 
> sender that you have received it in error. Unintended recipients are 
> prohibited from taking action on the basis of information in this 
> e-mail. E-mail messages may contain computer viruses or other defects, 
> may not be accurately replicated on other systems, or may be 
> intercepted, deleted or interfered with without the knowledge of the 
> sender or the intended recipient. If you are not comfortable with the 
> risks associated with e-mail messages, you may decide not to use 
> e-mail to communicate with IPC. IPC reserves the right, to the extent 
> and under circumstances permitted by applicable law, to retain, 
> monitor and intercept e-mail messages to and from its systems.
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180515/cd248c7f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 5400 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20180515/cd248c7f/attachment-0001.jpg>

More information about the Users mailing list