Well, actually the problem was the virtualization ... Virtio modules weren't loaded in my kernel, so i had slow performances for that reason. However thank you very much :) but i have posted also another question, about the dispatcher performances ... Basically i have a dispatcher in front of 2 proxies and i checked that it is actually able to manage just 2 Kamailio proxy istances (all the 3 components reaches 100% of CPU load with an equally distributed traffic). For which concern the DNS i checked that, by using Kamailio DNS cache mechanism, it is done just a single DNS query at the beginning of the call. Any suggestion? Or is it normal for the dispatcher to have this performance?
Andrea
On Fri, May 16, 2014 at 4:22 PM, Carsten Bock carsten@ng-voice.com wrote:
Just a quick idea: Did you check your DNS? Can you check, what DNS-queries are done and how long that takes? We had this issue once in another setup...
Kind regards, Carsten
2014-05-15 12:09 GMT+02:00 Andrea Meroni rucola8968@gmail.com:
The call is made from just one SIP account, and the limiting factor is
the
Proxy: 100% of CPU utilization, followed by the Dispatcher with a 90% ... The scheme is exactly the one you wrote. Do you think it is a problem of using just one account instead of different accounts?
Andrea
On Thu, May 15, 2014 at 10:43 AM, Carsten Bock carsten@ng-voice.com
wrote:
Hi Andrea,
can elaborate a little more:
- The Kamailio IMS-Core is making 500 Calls/Second.
- As soon as you add the dispatcher in front, you're down to 80
calls/second? Correct? If yes: Which system is the limiting factor? Does the dispatcher only process 80 calls/second or does the IMS-Core? The Setup is the following: Dispatcher => Proxy-CSCF => IMS-Core? If yes: Are the calls made from one SIP-Account or from random SIP-Accounts? Or are you using the Dispatcher for In-/Outbound calls (e.g. to the I-/S-CSCF)?
Thanks, Carsten
2014-05-15 11:17 GMT+02:00 Andrea Meroni rucola8968@gmail.com:
Hi all,
i have some strange performance issues (with Kamailio config file i guess): using the default configuration file i can reach a 500 call/s rate, while using the default configuration file in the dispatcher folder i can reach just a 80 call/s rate (using the dispatching failover algorithm ...). The dispatcher is in front on a very basic Kamailio-based IMS core. Something has some hint about this issues?
Andrea
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany
http://www.ng-voice.com mailto:carsten@ng-voice.com
Office +49 40 34927219 Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users