1 Jun
2007
1 Jun
'07
6:39 p.m.
On Wed, 2007-05-30 at 18:12 +0300, Daniel-Constantin Mierla wrote:
Hello,
On 05/30/07 17:49, David Coulthart wrote:
Daniel,
Thank you for this info. It appears switching to asynchronous
syslog'ing was a huge win for us.
We are currently experiencing problems with our
production OpenSER
(1.1.0) environment where the load on the server is steadily increasing
and the OpenSER response time increases drastically (e.g., 30+ seconds
for an internal call to ring).
this might be because of some slow DNS or database response. The best is
to run in higher debug mode to see where it gets stuck. Another
possiblity is the syslog, make sure it is configured to be asynchronous.
If you have lot of messages written to syslog synchronous, then you will
get lot of delays. To troubleshoot, see which application eats most of
the CPU, if that
happens.
On the other hand, with 1.2.x you get better performances and parsing
error handling via error_route. You should consider upgrading.
We are investigating 1.2.1. Better performance always sounds good.
Thx,
David Coulthart