Hmm, useful tip. Well worth noting for performance
reasons.
I wonder, do you know if this could have an effect on how information
is logged to the log file?
I am logging in real-time in synchronous mode to a custom log
file (using quite a few xlog statements in a routing block) on one of
our servers as well, and I am seeing fragmentation in the log messages
under high traffic. Timestamps and log messages all skewered and
mangled together.
On 11/6/06, *Daniel-Constantin Mierla* <daniel(a)voice-system.ro
<mailto:daniel@voice-system.ro>> wrote:
I guess it is related to your syslog daemon rather than to xlog
functions. Is your syslog configured asynchronous?
http://voice-system.ro/docs/ser-syslog/ar01s06.html
Cheers,
Daniel
On 11/06/06 05:05, Christian Schlatter wrote:
I recently did some performance testing with
openser 1.1 and
stumbled
over a rather strange thing. The xlog command
from the xlog module
seems to cause a huge performance penalty.
I have a rather complex config with many routing blocks and mysql
queries with which I can achieve up to 100 calls per second
(authenticated INVITEs) per openser instance. As soon as I add *one*
xlog statement to the config the cps rate goes down to 25, and the
average SIP message response time goes up from <10ms to >200ms.
Has anyone else observed this behavior or could this issue be caused
by a misconfiguration?
thanks,
Christian
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org <mailto:Users@openser.org>
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org <mailto:Users@openser.org>
http://openser.org/cgi-bin/mailman/listinfo/users