14 Dec
2010
14 Dec
'10
9:48 p.m.
Hello,
On 12/13/10 3:48 PM, michel freiha wrote:
Hello Daniel,
We are not facing any database problem even we are not using DNS
anywhere in Kamailio config...The only thing is that the debug level
is 2 and syslog was not configured asynchronous...Do you think if we
configure it as asynchronous, our issue will be solved?
debug=2 should be that
verbose to influence the performances in this
way. Anyhow is good to have syslog asynchonous. You can start with
log_stderror=yes to see if there is any improvement -- in this way you
know whether is an logging speed issue or not.
The solution to identify which piece of config is slow is to use
benchmark module.
Cheers,
Daniel
Regards
On Mon, Dec 13, 2010 at 1:08 PM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
On 12/10/10 4:15 PM, michel freiha wrote:
Hello Sir,
The crash issue has been successfully fixed after using GIT
for the version 3.1.0.
thanks for reporting back.
Now we have another problem..>When the number of registered
users exceeded 2500 concurrent registered users, the kamailio
stuck and each call will take up to 1 minute to be established
Any comment on that?
Do you have high debug level? If yes, is your syslog configured
asynchronously?
Other than that, you can use benchmark module to spot which of
your config actions takes so long to execute. Normally, such cases
can happen when you have queries to slow database or dns servers.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com