[SR-Users] Log levels severely impacts performance

Amit amit at brytecall.com
Wed Sep 14 04:18:02 CEST 2022


We’ve been running Kamailio 5.5.0 for a while now and recently ran into an issue where the application buffer would get full and Kamailio has a lot of difficulty keeping up with REG requests. This severely impacted Kamailio’s ability to perform and resulted in many REG timeouts.

Running ‘watch netstat -ulpn’ revealed the buffer issue.

We usually run the production system at log level INFO (2) and had not ran into any issues in the past.

When the buffer issue occurred and after some testing, we discovered that changing the log level to NOTICE (1) was sufficient to bring the system back into operational status.

For example, at log level INFO (2) we seem to achieve ~150-200 REG/s while at log level NOTICE (1) we reach ~500-700 REG/s.

I did find this article in the wiki and tried using the “-“ in front of the log path but this didn’t seem to help.

Even writing the logs directly to our external log server and preventing them from being written to the local disk doesn’t seem to alleviate the issue when the log level is set to INFO (2).

Does anyone have any experience with this or have any suggestions? We are finding it difficult to scale as a result of this issue.

Thank you in advance.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220914/56510e88/attachment.htm>

More information about the sr-users mailing list